What problem does it solve? After architecture review, programmers need a single actionable reference of what they must do and must never do per system layer, but ADRs explain reasoning rather than rules. This Skill extracts every required pattern, forbidden approach, and performance guardrail from Accepted ADRs, technical preferences, and engine reference docs into one flat control manifest. ## Core Features & Use Cases - Rule Extraction from ADRs: Parses all Accepted ADRs and pulls required patterns, rejected alternatives, performance budgets, and engine API constraints, each traced to its source ADR. - Layer-Based Organization: Classifies rules into Foundation, Core, Feature, and Presentation layers plus cross-cutting naming conventions, budgets, approved libraries, and forbidden APIs. - Gated Review Workflow: Presents a rule summary for confirmation, optionally runs a technical-director review gate (TD-MANIFEST) in full mode, and asks before writing docs/architecture/control-manifest.md. - Use Case: After your Godot project's architecture review passes with eight Accepted ADRs, run this Skill to produce a control manifest that story authors and programmers consult when writing implementation notes. ## Quick Start Ask the AI to run the create-control-manifest skill to extract rules from all Accepted ADRs and write the control manifest for this project.