architecture-decision

Architecture decisions are documented as Architecture Decision Records (ADRs) to track context, alternatives, and consequences. This skill guides you through structured phases to produce a committed ADR file that links to PRD requirements for durable traceability.

Creating an ADR for mobile architecture involves capturing framework references and version notes. This skill structures the decision workflow, generating a file at docs/architecture/ADR-NNNN-<slug>.md that cross-references framework documentation.

Linking an Architecture Decision Record to PRDs and existing ADRs ensures consistency and traceability. The skill guides you through validation and registry updates, cross-referencing relevant PRD requirements and prior decisions within the generated documentation.

An ADR file should include context, alternatives, the decision, consequences, and PRD requirements addressed. This skill enforces that structure through a guided workflow, outputting a markdown file under the docs/architecture/ directory.

You need to provide a short slug, such as state-management, when generating architecture documentation. The skill uses this slug to name the output file ADR-NNNN-<slug>.md and organizes it within the docs/architecture/ path.

You can use this ADR workflow to align framework-version notes with product requirements. The generated Architecture Decision Record explicitly maps technical choices to PRD requirements and framework references for validation and registry updates.