create-control-manifest

Generate a layered control manifest from Accepted ADRs and engine references.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill create-control-manifest-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/create-control-manifest
Command: npx skills add https://github.com/easonlao/jiazi-game --skill create-control-manifest-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts scattered architecture decisions and technical preferences into a single, flat, programmer-friendly rule sheet so teams can consistently follow the intended system constraints without rereading every ADR.

Core Features & Use Cases

  • Extracts rules from Accepted ADRs: Pulls required, forbidden, performance, and engine-compatibility constraints from docs/architecture/adr-*.md.
  • Incorporates technical preferences and engine references: Adds naming conventions, budgets, forbidden patterns, and deprecated API entries from the configured reference files.
  • Produces a layered control manifest: Organizes the output by architectural layer (Foundation, Core, Feature, Presentation) plus global rules, and writes it to docs/architecture/control-manifest.md.
  • Includes a director review gate: Uses a technical-director task in review modes to validate rule completeness and provenance before writing.

Quick Start

Regenerate the manifest by running create-control-manifest with the update instruction so the output at docs/architecture/control-manifest.md reflects the latest Accepted ADRs.

Frequently Asked Questions about create-control-manifest

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

FAQPage Schema
How do I extract enforceable engineering rules from accepted ADRs?

A control manifest extracts required, forbidden, performance, and engine-compatibility constraints from Accepted ADRs, converting scattered architecture decisions into a single flat rule sheet for programmers to follow system constraints without rereading every ADR.

How do I generate a control manifest for Godot project architecture layers?

Generate a control manifest by loading ADR files and engine reference docs to collect deprecated APIs and naming conventions, then organizing extracted rules by Foundation, Core, Feature, and Presentation layers before writing to `docs/architecture/control-manifest.md`.

What is the purpose of a technical review gate in architecture documentation?

A technical review gate validates rule completeness and provenance through a `technical-director` task before writing the control manifest, ensuring programmers receive verified "what to do/never do" guidance per architectural layer.

Can I include engine compatibility and deprecated API constraints in a control manifest?

Yes, the control manifest incorporates engine version details and deprecated API entries from configured reference files alongside naming conventions and forbidden patterns extracted from technical preferences and ADRs.

How do I update a control manifest to reflect the latest architecture decisions?

Run the update instruction to regenerate the control manifest, ensuring the output at `docs/architecture/control-manifest.md` reflects the latest Accepted ADRs and technical preferences after your architecture review workflow.

What format does a control manifest use to organize architectural rules?

A control manifest uses a flat, actionable markdown format that organizes rules by architectural layer—Foundation, Core, Feature, Presentation—plus global rules, written directly to `docs/architecture/control-manifest.md`.