create-control-manifest

Convert Accepted ADRs and engine references into a layered programmer rules sheet.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill create-control-manifest-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/create-control-manifest
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill create-control-manifest-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from missing or misapplying architectural decisions by converting Accepted ADRs, technical preferences, and engine reference constraints into a single, flat set of actionable rules programmers can follow.

Core Features & Use Cases

  • Extracts required and forbidden rules: Pulls “must/should/required to/always” requirements and rejected alternatives (as “never” rules) directly from Accepted ADRs.
  • Adds performance and engine constraints: Captures performance guardrails and engine API compatibility rules, including forbidden APIs from deprecated-apis documentation.
  • Organizes by architectural layer: Classifies rules into Foundation, Core, Feature, Presentation, plus Global rules for cross-cutting constraints.
  • Uses a technical director gate: Summarizes rule counts and coverage, then routes a review/approval decision before writing the manifest.

Quick Start

Run the create-control-manifest skill after architecture review is complete and ADRs are in Accepted status to generate docs/architecture/control-manifest.md.

Frequently Asked Questions about create-control-manifest

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

FAQPage Schema
How do I convert accepted ADRs into actionable programmer rules?

Converting accepted ADRs into programmer rules involves extracting required and rejected alternatives into a flat rules sheet. The process organizes these constraints by architectural layer, adding performance guardrails and engine API compatibility rules for traceable compliance.

What is a control manifest in software architecture?

A control manifest is a flat rules sheet generated from accepted ADRs and engine reference documentation. It categorizes architectural constraints into Foundation, Core, Feature, Presentation, and Global layers to provide programmers with traceable, actionable directives.

How do I enforce engine API compatibility and deprecated API restrictions?

Enforce engine API compatibility by integrating deprecated-apis documentation into your rules extraction workflow. This captures forbidden API entries and adds them to the control manifest, ensuring programmers actively avoid outdated engine interfaces.

Can I generate a control manifest before ADRs are in Accepted status?

Generating a control manifest before ADRs are in Accepted status is not possible. The extraction workflow requires an architecture review with accepted ADRs and a present engine reference version to ensure rules are traceable to finalized decisions.

How do I add a technical director approval gate before writing architecture files?

Adding a technical director approval gate involves generating a preview with layer counts and coverage summaries before writing the final file. This gate routes a review decision, ensuring the manifest meets standards before saving to docs/architecture/control-manifest.md.

What is the best way to organize technical documentation for game engine guardrails?

Organizing game engine guardrails is best achieved by classifying them into Foundation, Core, Feature, and Presentation layers, plus Global rules for cross-cutting constraints. This structure maps engine performance limits directly to architectural boundaries.