create-control-manifest

To generate a control manifest from accepted ADRs, run the skill after architecture review passes. It extracts required, forbidden, and performance rules, outputting a flat checklist to docs/architecture/control-manifest.md.

A programmer-ready rules sheet is a flat control manifest that converts accepted ADRs and engine reference guidance into actionable implementation rules, forbidden approaches, and performance budgets organized by architectural layer.

Yes, you can enforce forbidden APIs and performance budgets by extracting guardrails from accepted ADRs. The manifest pins engine-specific compatibility constraints and collects time/memory budgets for ongoing development.

To organize implementation rules by architectural layer, the control manifest categorizes extracted ADR guidelines into Foundation, Core, Feature, and Presentation layers, adding global cross-cutting constraints for consistent implementation.

Yes, a technical director gate is required before generating a control manifest. The skill gates technical review before writing, ensuring accepted ADRs and architecture review have passed before producing the rules sheet.

A limitation of generating a control manifest is that it only processes ADRs with Status: Accepted. If architecture review has not passed or ADRs lack implementation guidelines, the output manifest will be incomplete.