Does this skill follow a specific ADR template?

Yes, it uses a standardized template including Context, Decision, Consequences, and a Change Log to ensure consistent and high-quality documentation.

Where does this skill store architectural decisions?

Decisions are stored in the 'docs/ADR/' directory, using a naming convention of 'YYYYMMDD-title.md' for easy chronological tracking.

How does the skill handle task decomposition?

The skill triages task size; if a task is complex enough to be decomposed, it drafts a plan for user confirmation before starting any coding work.

Is the plan updated during the coding process?

Yes, PLAN.md is treated as a living document and is updated frequently to reflect the current status and any changes in implementation reality.

What is the primary purpose of the Plan & ADR Flow skill?

It is designed to ensure that technical tasks are properly planned in a PLAN.md file and that significant architectural decisions are recorded as ADRs before and during implementation.

Plan & ADR Workflow

Name: Plan & ADR Workflow
Author: fyuuki0jp

byfyuuki0jp

0•

생산성 및 워크플로

Standardizes the planning and documentation of technical decisions using PLAN.md and Architectural Decision Records (ADRs).

This skill formalizes the development process by integrating task decomposition and architectural documentation directly into your repository. It guides Claude to triage task complexity, maintain a living 'PLAN.md' at the root, and record significant technical choices in 'docs/ADR/' using a standardized template. This ensures that every implementation is backed by a clear strategy and a permanent record of why specific decisions were made, significantly improving long-term maintainability and team alignment.

주요 기능

01Standardized Architectural Decision Record (ADR) creation

020 GitHub stars

03Living PLAN.md management for real-time progress tracking

04Automated directory management for technical documentation

05Automated task triage and decomposition strategy

06Persistent technical decision history with additive change logs

사용 사례

01Recording architectural rationale and trade-offs for future project maintainers

02Breaking down complex coding tasks into manageable, documented implementation steps

03Maintaining a synchronized implementation plan during rapid prototyping or refactoring

주요 기능

01Standardized Architectural Decision Record (ADR) creation

020 GitHub stars

03Living PLAN.md management for real-time progress tracking

04Automated directory management for technical documentation

05Automated task triage and decomposition strategy

06Persistent technical decision history with additive change logs

사용 사례

01Recording architectural rationale and trade-offs for future project maintainers

02Breaking down complex coding tasks into manageable, documented implementation steps

03Maintaining a synchronized implementation plan during rapid prototyping or refactoring