Document an architecture or design decision
/plugin marketplace add asermax/claude-plugins/plugin install katachi@asermax-pluginsDocument an architecture decision (ADR) or design pattern (DES).
Skill to load:
Load the katachi:framework-core skill for workflow principles and decision type guidance.
Feature inventory:
@planning/FEATURES.md - Feature definitions (to check for affected features)
Decision indexes:
@docs/architecture/README.md - Architecture decisions (ADRs)
@docs/design/README.md - Design patterns (DES)
Ask user what they want to document:
"What kind of decision are you documenting?
A) Architecture Decision (ADR)
- Hard-to-change technical choices
- Technology selections, patterns, approaches
- One-time decisions with significant consequences
B) Design Pattern (DES)
- Repeatable patterns across the codebase
- Conventions, coding patterns, cross-cutting concerns
- Patterns that should be consistent
Which type fits your decision?"
Ask about the decision:
For DES, also ask:
If user is uncertain about alternatives or consequences:
Create complete document following appropriate template.
For ADR:
For DES:
Show draft document to user. Highlight any uncertainties. Ask: "What needs adjustment?"
Apply user corrections. Repeat until approved.
Determine next available ID:
docs/architecture/docs/design/Add to appropriate README index:
For ADR in docs/architecture/README.md:
For DES in docs/design/README.md:
Write to appropriate location:
docs/architecture/ADR-NNN-title.mddocs/design/DES-NNN-pattern-name.mdAsk:
"Which features should reference this decision?
I'll update their designs to reference this [ADR/DES]."
Note features to update.
This is a collaborative process: