What problem does it solve?
It converts scattered architecture decisions and technical preferences into a single, flat, programmer-friendly rule sheet so teams can consistently follow the intended system constraints without rereading every ADR.
Core Features & Use Cases
- Extracts rules from Accepted ADRs: Pulls required, forbidden, performance, and engine-compatibility constraints from
docs/architecture/adr-*.md.
- Incorporates technical preferences and engine references: Adds naming conventions, budgets, forbidden patterns, and deprecated API entries from the configured reference files.
- Produces a layered control manifest: Organizes the output by architectural layer (Foundation, Core, Feature, Presentation) plus global rules, and writes it to
docs/architecture/control-manifest.md.
- Includes a director review gate: Uses a
technical-director task in review modes to validate rule completeness and provenance before writing.
Quick Start
Regenerate the manifest by running create-control-manifest with the update instruction so the output at docs/architecture/control-manifest.md reflects the latest Accepted ADRs.