create-control-manifest

To turn accepted ADRs into a control manifest, compile accepted architecture decisions, technical preferences, and engine references into a flattened file. This enforces naming conventions, performance budgets, and deprecated APIs with cited sources across foundation, core, feature, and presentation layers.

Consolidating architecture decisions for governance involves synthesizing accepted ADRs and engine references into a single source of truth. The output categorizes enforceable guidelines into foundation, core, feature, and presentation layers, plus global constraints, to support deterministic development workflows.

Enforce naming conventions and performance budgets by generating a control manifest that maps rules to foundation, core, feature, and presentation layers. The manifest extracts constraints from accepted ADRs and engine-specific API rules, citing sources for each guideline.

Generating a control manifest works without external dependencies or components. The skill synthesizes accepted ADRs, technical preferences, and engine references internally to output a comprehensive governance file at docs/architecture/control-manifest.md.

You need a flattened control manifest instead of individual ADRs when ensuring consistency across deterministic development workflows. It extracts rules from accepted ADRs and engine references, categorizing them by application layer and global constraints to provide a single, actionable source of truth.

Deprecated APIs and engine-specific constraints must be included in architecture documentation to enforce guardrails and prevent inconsistent implementations. The control manifest formalizes these constraints from accepted ADRs and engine references, ensuring engineers follow deterministic, compliant development workflows.