skills/creating-adrs/SKILL.md
Structured ADR creation in MADR format. Use when: ADR, Architecture Decision, 決定記録, 技術選定, アーキテクチャ決定, deprecation, 非推奨化.
npx skillsauth add thkt/claude-config creating-adrsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Phase | Actions |
| ------------- | ------------------------------------------------------------------------ |
| 1. Pre-Check | Run ./scripts/pre-check.sh "$TITLE" (uses shared scripts) |
| 2. Template | Run $HOME/.claude/scripts/select-adr-template.sh "$TITLE" |
| 3. References | Gather project docs, issues, external resources |
| 4. Validate | Check required sections (Title, Status, Context, Decision, Consequences) |
| 5. Index | Auto-generate adr/README.md |
| 6. Recovery | Handle missing dirs, duplicates, missing sections |
Use script to auto-select template:
TEMPLATE=$("$HOME/.claude/scripts/select-adr-template.sh" "$TITLE")
| Template | Use Case | Required Sections | | -------------------- | -------------------------- | -------------------------- | | technology-selection | Library, framework choices | Options (min 3), Pros/Cons | | architecture-pattern | Structure, design policy | Context, Consequences | | process-change | Workflow, rule changes | Before/After comparison | | deprecation | Retiring technology | Migration plan, Timeline |
adr/
├── README.md # Auto-generated index
├── 0001-*.md # Sequential numbering
└── 0002-*.md
| Rule | Detail |
| ------------ | ------------------------------------------------------------------------------------------- |
| Immutability | Once accepted, never modify. To change, create a new ADR that supersedes it |
| Brevity | Target ~80 lines. Context: 3 lines. Options: 3-5 lines each. Consequences: 2-3 bullets |
| Confidence | - Confidence: {level} — {rationale} in metadata. Level + reason in one line |
| Reassessment | Optional ## Reassessment Triggers section after Consequences |
| Level | When to use | | ------ | -------------------------------------------------------- | | high | All options evaluated, clear winner, team consensus | | medium | Some unknowns remain, limited production data | | low | Best guess under constraints, significant unknowns exist |
| Topic | Resource |
| --------- | ----------------------------- |
| MADR | https://adr.github.io/madr/ |
| Fowler | https://martinfowler.com/articles/architecture-decision-record.html |
| Skill | ../adr/SKILL.md |
| Templates | ../../templates/adr/ |
| Scripts | ./scripts/ |
tools
Internal helper for /think Step 11. Renders SOW.md + Spec.md as an integrated Astro view and returns a dev server URL.
development
Extract repository spec while detecting bugs, spec gaps, and consistency drift via dual-purpose documentation. OUTCOME.md-axis question-driven exploration with ephemeral output. Do NOT use for code review (use /audit or /polish), feature implementation (use /code), planning only (use /think), or single-bug fix (use /fix).
development
Discover undocumented design decisions and challenge each candidate via critic-design before promotion. Rank by impact and reversibility, produce ADR promotion candidates. Treat each candidate as a position arguing for ADR status, not a fact to be filed. Pairs with audit-adr-drift, which scans existing ADRs for drift against code.
development
Scan ADR Decision sections against current code and report drift with modification direction and priority. Do NOT use for repos without ADRs (use audit-adr-gaps instead).