architecture-decision

This skill transforms accepted architecture decision records into a single, layer-organized reference guide that tells programmers exactly what to do and what to avoid. It pulls rules from ADRs, technical preferences, and engine docs, then surfaces them by Foundation, Core, Feature, and Presentation layers—answering "what do I do?" faster than reading the reasoning behind each decision.

The ADR skill helps you record major architectural choices in a structured format that captures the reasoning behind decisions, not just the outcome. It stores numbered records in your project's docs folder and guides you through context, trade-offs, and consequences so your team can understand why decisions were made.

When a game design document is revised, architectural decisions built on it may become stale. This skill reads the changed GDD, compares it against all architecture decision records, and produces a detailed impact report classifying each ADR as still valid, needing review, or likely superseded. It then guides you through resolution decisions and updates your traceability index.

Create Epics transforms approved design documents and architecture into named, bounded epics—one per architectural module. Each epic defines scope, identifies governing architecture decisions, flags engine risk, and traces requirements to decision coverage. Run this skill once per development layer after control manifest and architecture review pass; follow each epic with /create-stories to decompose into implementable work.

This skill guides you through creating Architecture Decision Records for Java projects via structured dialogue. It systematically gathers decision context, stakeholder input, and architectural trade-offs, then produces a MADR-formatted document capturing your choice and rationale.

This skill guides you through writing Architecture Decision Records—concise documents that capture the shape of load-bearing choices, why you made them, and what trade-offs you considered. Use it when a decision is hard to reverse, surprising without context, or the result of genuine alternatives. ADRs live in docs/adr/ with sequential numbering and a simple template; most need just a paragraph.