architecture-decision
This skill guides you through authoring Architecture Decision Records (ADRs) that capture major technical choices with full context. It validates decisions against existing architectural stances, engine compatibility, and GDD requirements, then generates a structured record with status, dependencies, and consequences tracked. Use it to retrofit missing sections into existing ADRs or create new ones from scratch.
architecture-decision creates a formal record documenting significant technical choices, their context, alternatives, and consequences.
AI-generated summary based on this skill's SKILL.md
Install
Donchitos/Claude-Code-Game-Studios/architecture-decision · repository language: Shell
git clone https://github.com/Donchitos/Claude-Code-Game-Studios
cp -r Claude-Code-Game-Studios/.claude/skills/architecture-decision ~/.claude/skills/architecture-decisionnpx skillfed install Donchitos/Claude-Code-Game-Studios/architecture-decisionFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create an architecture decision record with this skill?
architecture-decision guides you through authoring Architecture Decision Records that capture major technical choices with full context. Start by describing your significant technical choice, and the skill will help you structure it with status, dependencies, and consequences. It validates your decision against existing architectural stances and engine compatibility constraints, then generates a formal ADR document ready for your architecture registry.
Can architecture-decision retrofit existing ADRs with missing sections?
Yes. architecture-decision validates and retrofits existing ADRs by identifying missing sections like Status and Dependencies. Provide your current ADR, and the skill will enhance it with complete coverage, ensuring all critical fields are documented and your decision is properly linked to GDD requirements and system dependencies.
What should I document in an ADR for a design decision?
architecture-decision helps you document technical decisions and consequences comprehensively. Include the decision context, alternatives you considered, the chosen solution, its consequences, engine compatibility constraints, and dependencies on other architectural stances. The skill ensures your ADR captures performance implications, interface contracts, and traceability back to GDD requirements.
How does architecture-decision handle engine compatibility in ADRs?
architecture-decision documents ADRs with engine compatibility constraints built in. When you describe your technical choice, specify any compatibility requirements or limitations. The skill validates these against your system's known constraints and includes them in the formal record, ensuring your architecture registry reflects all compatibility implications.
Can this skill link my ADR to GDD requirements and dependencies?
architecture-decision links architectural decisions to GDD requirements and system dependencies automatically. It updates your architecture registry with new stances and interface contracts from your decisions, creating traceability between your technical choices and the broader system design. This ensures decisions remain aligned with requirements.
What format does architecture-decision use for the final ADR?
architecture-decision generates structured Architecture Decision Records with all standard sections: decision context, alternatives considered, chosen solution, consequences, status, dependencies, and engine compatibility notes. The formal output is ready for immediate inclusion in your architecture registry and can be validated against existing architectural stances.
SKILL.md
rendered from the published skill — quoted content, verbatim
When this skill is invoked:
0. Parse Arguments — Detect Retrofit Mode
Resolve the review mode (once, store for all gate spawns this run):
1. If --review [full|lean|solo] was passed → use that
2. Else read production/review-mode.txt → use that value
3. Else → default to lean
See .claude/docs/director-gates.md for the full check pattern.
If the argument starts with retrofit followed by a file path
(e.g., /architecture-decision retrofit docs/architecture/adr-0001-event-system.md):
Enter retrofit mode:
- Read the existing ADR file completely.
- Identify which template sections are present by scanning headings:
## Status— BLOCKING if missing:/story-readinesscannot check ADR acceptance## ADR Dependencies— HIGH if missing: dependency
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/architecture-decision/SKILL.md