Skip to content
v3.4.0

AI Unified Process core - stack-agnostic requirements, entity model, and use cases, plus the construction orchestrators for layer plugins

architecture-decision

Records architecture decision records (ADR-XXX) in docs/architecture/decisions/, each one linked to the non-functional requirements (NFR-) and constraints (C-) of docs/requirements.md it serves: drafts an ADR from a decision stated in plain words (Context, Decision, Consequences), checks it against the accepted ADRs for contradictions and overlaps, supersedes an earlier ADR on request, moves an ADR through Proposed, Accepted, Superseded, Deprecated, and Rejected, and lists the ADRs filtered by requirement or status. Use when the user asks to "record an ADR", "write an architecture decision", "document why we chose X", "we decided to use jOOQ instead of JPA", "supersede ADR-002", "accept ADR-005", "list the ADRs", "which ADRs depend on C-005", or mentions architecture decision records, ADRs, or docs/architecture/decisions. Also trigger when the user states a technology or structure decision in conversation that the project should remember. A question about the specification is /open-questions, not an ADR.

Read SKILL.md at the source

Pinned to revision dbb4e27b6d25, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.