create-control-manifest

You can create a control manifest by extracting rules from accepted ADRs and architecture documentation. It groups decisions by layers like Presentation, Domain, and Infrastructure, outputting a markdown file for code reviews and sprint planning.

A control manifest is an authoritative rules sheet that replaces scattered architecture documents. It codifies decisions from accepted ADRs into a single document, serving as a concrete reference for engineers during implementation and sprint planning.

To keep architecture rules traceable during code reviews, generate a control manifest that ensures every rule cites a source ADR or architecture document. This provides a centralized reference for engineers to verify implementation decisions.

Yes, you can group architecture decisions by layer and system for sprint planning. The manifest extracts rules across Presentation, State, Domain, Data, and Infrastructure layers, and by systems like auth and payments.

You should regenerate the architecture control manifest when ADRs change to reflect the latest decisions. Run the generation process after the architecture review passes to update the output file with current rules.

Generating an ADR control manifest requires no external dependencies. It processes accepted ADRs and architecture documentation directly to output the manifest file, making it easy to adopt in any software engineering environment.