create-control-manifest

You can generate a control manifest by compiling rules from accepted ADRs, technical preferences, and engine reference docs. The skill parses these architectural documents to produce a flat, actionable rules sheet for programmers.

A control manifest is a flat, actionable rules sheet organized by architectural layer. You need it after architecture is complete to ensure programmers understand what must and must not be done across Foundation, Core, Feature, and Presentation layers.

Compiling ADR rules and technical preferences into programming guidelines involves pulling rules from accepted ADRs and engine reference docs. The skill interprets this content and organizes it into a unified ruleset by architectural layer.

Yes, you can organize programming guidelines by architectural layer using existing architecture documentation. The skill structures rules into Foundation, Core, Feature, and Presentation layers, making the manifest easily navigable for backend development.

Yes, generating a control manifest requires access to architectural documents, accepted ADRs, technical preferences, and engine reference docs. The skill must parse and interpret this document content to organize data and produce output files.

The best way to enforce architecture documentation rules is to generate a flat, actionable control manifest. This sheet compiles ADR rules and technical preferences, providing clear programming guidelines organized by architectural layer.