create-control-manifest

To generate a developer-facing control manifest from accepted ADRs, run the control manifest generation skill. It extracts rules from ADRs, technical preferences, and engine references, outputting a flat actionable sheet to docs/architecture/control-manifest.md.

A control manifest in software architecture is a flat, actionable rules sheet for programmers extracted from accepted ADRs. It specifies required patterns, forbidden approaches, and performance guardrails, being more immediately actionable than ADRs which only explain why.

To map architecture rules to Foundation, Core, Feature, and Presentation layers, use automated manifest generation. It aggregates global conventions, deprecated APIs, and best practices, applying per-layer mapping and gating to ensure consistent implementation across modules.

Yes, the control manifest supports engine references and technical preferences for Godot projects. It automates rule generation from accepted ADRs and engine docs, mapping required patterns and forbidden approaches across architectural layers to guide programmers.

You need to generate a flat actionable manifest for developer handoffs when an ADR is accepted and the project requires a developer-facing reference. This ensures programmers implement across modules with consistent rules across Foundation, Core, Feature, and Presentation layers.

Yes, you can use architecture review workflows to enforce deprecated APIs and performance guardrails. The manifest generation applies gating and global rules, aggregating technical preferences and engine references into a centralized reference for consistent module implementation.