create-control-manifest

Generates a layered rules manifest for programmers from accepted architecture decision records.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill create-control-manifest-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/create-control-manifest
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill create-control-manifest-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about create-control-manifest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn architecture decision records into coding rules?

Run this Skill after your ADRs reach Accepted status. It extracts every must-do and never-do statement from the ADRs, classifies them by architectural layer, and writes a control manifest at docs/architecture/control-manifest.md with each rule traced to its source ADR.

What is a control manifest in game development?

A control manifest is a flat programmer reference listing required patterns, forbidden approaches, and performance guardrails per architectural layer. Unlike ADRs, which explain why decisions were made, the manifest states what programmers must do when implementing stories.

When should I regenerate the control manifest?

Regenerate it whenever new ADRs are accepted or existing ADRs are revised. The manifest embeds a version date that story-readiness checks compare against, so stale manifests cause stories written against outdated rules to be flagged.

Does the control manifest skill work with Godot and Unity projects?

Yes, it reads engine reference docs under docs/engine-reference for whichever engine and version your project pins, including deprecated API lists. Forbidden API entries in the manifest come directly from those engine-specific reference files.

What happens if the technical director review rejects the manifest?

In full review mode, a REJECT verdict blocks writing the manifest entirely. You must fix the flagged rules, re-present the summary, and pass the TD-MANIFEST gate before the file is written.