What problem does it solve? Engineering teams lose track of why decisions were made and how designs evolved because proposals, ADRs, specs, and postmortems live in scattered, inconsistent documents. This Skill defines the doc lifecycle and per-folder conventions so every artifact follows a predictable status flow. ## Core Features & Use Cases - Lifecycle Conventions: Defines the flow from proposals (draft → fcp → accepted/rejected) to frozen ADRs, derived specs, and blameless postmortems, with guides as the how-to bucket. - Per-Folder Agent Behaviors: Encodes proactive rules such as surfacing stale draft proposals after 14 days, suggesting Supersedes links for new decisions, and stubbing guides from postmortem action items. - Workflow Routing: Points to five sibling skills (frame-a-proposal, write-a-spec, record-a-decision, write-a-postmortem, review-a-design) so procedural guidance loads only when needed. - Use Case: A team member asks how to document an accepted RFC; the Skill explains graduating the proposal into a MADR-shaped decision record and deriving a spec-kit style spec folder. ## Quick Start Ask the agent how to document a new design proposal in this project and follow the proposals folder conventions it describes.
