implement-adr

Decompose ADRs into staged tasks and generate plan.md files with estimates.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/juliusl/adr-skills --skill implement-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-adr
Source: https://github.com/juliusl/adr-skills/tree/main/src/skills/implement-adr
Command: npx skills add https://github.com/juliusl/adr-skills --skill implement-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Turns Architectural Decision Records into actionable implementation plans by decomposing ADRs into staged work, generating plan.md files with scoped tasks, cost estimates, and traceability back to the source decisions.

Core Features & Use Cases

  • Decompose ADR into staged tasks and plan structure.
  • Generate plan.md with tasks, estimates (small/medium/heavy), and ADR references.
  • Identify gaps and surface them for ADR creation or linkage, with explicit status transitions (Planned -> Accepted) during plan finalization.
  • Provide traceability from each task back to the source ADR sections.

Quick Start

Provide an ADR reference and I will generate a plan.md with tasks, estimates, and a finalization step.

Frequently Asked Questions about implement-adr

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

FAQPage Schema
How do I turn architectural decision records into actionable implementation plans?

To turn architectural decision records into actionable plans, you provide an ADR reference to generate a plan.md file containing staged tasks, effort estimates, and traceability links back to the source decisions.

What is the best way to decompose an ADR into staged development tasks?

Decomposing an ADR into staged tasks involves breaking down the decision into scoped actions, assigning cost estimates like small or heavy, and emitting per-task references to ensure full traceability throughout the implementation lifecycle.

How do I estimate effort and detect gaps when planning an architectural decision?

Effort estimation and gap detection happen during plan generation by assigning cost estimates to tasks and surfacing missing requirements for new ADR creation or linkage before finalizing the plan.

Can I track ADR lifecycle statuses like Planned and Accepted in my plan.md files?

Yes, you can track ADR lifecycle statuses by applying explicit status transitions from Planned to Accepted during plan finalization, ensuring implementation signals are updated directly within the plan workflow.

Does this approach work with ADR formats generated by author-adr?

Yes, this approach supports ADR formats generated by author-adr, allowing you to parse existing decision records and coordinate the output with plan-review and QA planning as part of the workflow.