<< All versions
Skill v1.0.1
currentAutomated scan100/100majiayu000/claude-skill-registry-data/plan-adr-flow
3 files
──Details
PublishedMay 26, 2026 at 08:08 AM
Content Hashsha256:7337d5bb3586b1b8...
Git SHAcb443017503a
Bump Typepatch
──Files
Files (1 file, 1.7 KB)
SKILL.md1.7 KBactive
SKILL.md · 58 lines · 1.7 KB
version: "1.0.1" name: plan-adr-flow description: Plan and document coding tasks with PLAN.md and ADRs in docs/ADR. Use when a task can be decomposed, when asked to create or update PLAN.md, or when capturing technical decisions.
Plan + ADR Flow
Goal
Keep task planning and technical decisions documented in PLAN.md and docs/ADR/... before, during, and after implementation.
Workflow
- Triage task size
- If the task is not meaningfully decomposable, proceed without creating
PLAN.mdor ADR unless requested. - If the task is decomposable, draft a plan and confirm with the user before implementation.
- Create plan and ADR when planning
- Create or replace
PLAN.mdat repo root with the implementation plan. - Create
docs/ADR/YYYYMMDD-title.mdfor the technical decision record before coding. - Create
docs/ADR/if missing. - Use a short, lowercase, hyphenated slug for
title.
- Update during implementation
- Treat
PLAN.mdas a living memo; update it frequently to reflect reality. - Append ADR updates when technical issues or new decisions appear; keep prior entries.
- Finalize after implementation
- Update ADR with outcomes, changes, and follow-ups.
- Mark
PLAN.mdas complete or reflect the final state.
ADR template (minimum)
markdown
# <Title>Date: YYYY-MM-DDStatus: Proposed | Accepted | Superseded## Context-<Why this decision is needed>## Decision-<What is decided>## Consequences-<Impact, tradeoffs, follow-ups>## Change log-YYYY-MM-DD: <What changed and why>
Notes
- Keep ADR updates additive; never delete past entries.
- Keep
PLAN.mdspecific to the current task; do not modifyPLANS.mdunless explicitly asked.