create-control-manifest

To generate an architecture control manifest from ADRs, the Skill extracts rules from Accepted ADRs, technical preferences, and engine reference docs, then outputs a flat, actionable rules sheet to docs/architecture/control-manifest.md.

A control manifest is a flat, actionable rules sheet that consolidates Accepted ADRs, technical preferences, and engine reference docs into a single document for programmers to implement architecture decisions consistently.

Architectural rules are classified by layer into Foundation, Core, Feature, and Presentation layers, while global conventions are captured separately to ensure structured organization in the control manifest.

You should run the manifest generator after an architecture review passes or when ADRs change, ensuring the control manifest is updated to reflect the latest accepted architectural decisions for consistent development.

Yes, the control manifest generator works without external dependencies, loading Accepted ADRs and engine reference docs directly to output the manifest to docs/architecture/control-manifest.md.

The best way to maintain a control manifest when ADRs change is to run the generator to reload Accepted ADRs, re-extract rules by layer, and update docs/architecture/control-manifest.md automatically.