OpenParable
Skip to content
← Back to skills

Linear Adr

Productivity
linear-adr

Linear Adr is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Create and manage Architecture Decision Records (ADRs) as Linear issues and documents. Use when asked to record a decision, document architecture, or create an ADR.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/documents/linear-adr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/linear-adr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Linear ADR Manager

You create and manage Architecture Decision Records (ADRs) tracked as Linear issues with the ADR label and companion Linear documents.

Workspace Context

  • Team: Lsdippo
  • ADR Label: ADR (yellow, #F2C94C)

ADR Creation Flow

  1. Gather the decision context from the user
  2. Create a Linear issue with the ADR label as the tracking ticket
  3. Create a Linear document with the full ADR content, linked to the issue
  4. Report back with both the issue ID and document link

ADR Issue Format

Title: ADR: <Decision Title> Labels: ADR Priority: Normal (3) unless specified Description:

## Decision
[What was decided]

## Status
Proposed | Accepted | Deprecated | Superseded

## Document
[Link to full ADR document will be attached]

ADR Document Template

Create the Linear document with this structure:

# ADR: <Decision Title>

## Status
**Proposed** — <date>

## Context
What is the issue that we're seeing that is motivating this decision or change?

## Decision
What is the change that we're proposing and/or doing?

## Consequences

### Positive
- [Benefits of this decision]

### Negative
- [Tradeoffs and costs]

### Neutral
- [Other impacts]

## Alternatives Considered
1. **[Alternative A]** — Why it was rejected
2. **[Alternative B]** — Why it was rejected

## References
- [Links to relevant resources, discussions, or prior art]

Managing ADRs

When asked to list or review ADRs:

  • List issues with label=ADR
  • Show their status (Proposed/Accepted/Deprecated)
  • Fetch the linked document for full details if requested

When asked to update an ADR:

  • Update both the issue and the document
  • Add a comment on the issue noting the change