plan-adr

Decompose accepted ADRs into sequenced Linear issues under a parent Epic.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jamesc/skills --skill plan-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-adr
Source: https://github.com/jamesc/skills/tree/main/skills/plan-adr
Command: npx skills add https://github.com/jamesc/skills --skill plan-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms high-level Architectural Decision Records (ADRs) into a series of concrete, sequenced, and agent-ready implementation issues, streamlining the development process.

Core Features & Use Cases

  • ADR Analysis: Identifies affected components and natural implementation phases from an ADR.
  • Issue Breakdown: Creates a dependency graph for tasks, ensuring logical progression.
  • Epic & Issue Creation: Generates a parent Epic and detailed child issues in Linear, complete with acceptance criteria and file scope.
  • Use Case: When a new ADR is accepted, use this skill to automatically generate all the necessary development tickets, linked together and ready for the engineering team to pick up.

Quick Start

Use the plan-adr skill to plan the implementation of ADR number 123.

Frequently Asked Questions about plan-adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down an Architectural Decision Record into actionable development issues?

Creating Linear issues from an ADR involves decomposing the accepted document into a structured set of actionable tasks. This Skill generates a parent Epic and child issues via the Linear GraphQL API, complete with acceptance criteria and file modification scopes.

Can I automatically generate a dependency graph for ADR implementation tasks in Linear?

Generating ADR implementation tasks includes creating a dependency graph to ensure logical progression. The Skill maps out inter-issue dependencies, acceptance criteria, and out-of-scope definitions before creating the linked Linear issues.

What is included in the Linear issue descriptions when planning ADR implementation?

When planning ADR implementation, issue descriptions include context, acceptance criteria, files to modify, and out-of-scope definitions. The Skill updates the original ADR with implementation tracking details after creating the Epic and child issues.

Does planning ADRs into Linear issues require manual epic creation after analysis?

Planning ADRs into Linear issues automates epic creation entirely. The Skill uses the Linear GraphQL API to create the parent Epic and child issues, then updates the ADR document with implementation tracking details without manual intervention.

How do I track the implementation progress of accepted ADRs across development phases?

Tracking ADR implementation progress is handled by updating the ADR with implementation tracking details after issue creation. The Skill identifies natural implementation phases and creates sequenced Linear issues, providing a clear development workflow.