create-control-manifest

Name: create-control-manifest
Availability: InStock
Author: dnkrow

Extract required and forbidden rules from Accepted ADRs into a control manifest.

1|Updated May 15, 2026

Search Tags:#architecture #documentation automation #technical preferences #quality governance #adr extraction #rules synthesis #engine constraints

Ready to run

npx skills add https://github.com/dnkrow/skill --skill create-control-manifest-dnkrow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/dnkrow/skill/tree/main/claude-global/create-control-manifest
Command: npx skills add https://github.com/dnkrow/skill --skill create-control-manifest-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of translating architecture decisions into a single, practical checklist that programmers can follow immediately—without repeatedly reading multiple ADRs to learn what to do and what to avoid.

Core Features & Use Cases

Extracts actionable rules from Accepted ADRs: Pulls required patterns, forbidden approaches, performance guardrails, and engine/API constraints, organized by architectural layer.
Integrates technical preferences and engine reference: Adds naming conventions, performance budgets, forbidden patterns, deprecated APIs, and any best practices available.
Produces a flat control manifest for fast implementation: Writes a programmer quick-reference to docs/architecture/control-manifest.md.

Quick Start

Run create-control-manifest to generate an updated docs/architecture/control-manifest.md after your ADRs are in Accepted status.

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 actionable rules from accepted ADRs for developers?▼

A control manifest is a flat, programmer-ready rules sheet that extracts required and forbidden constraints from Accepted ADRs, technical preferences, and engine reference documents. It organizes rules by architectural layer so developers avoid repeatedly reading multiple ADRs.

How do I generate a programmer-ready control manifest from architecture decisions?▼

Generate a control manifest by reading Accepted ADR files, consuming technical preferences and engine reference documents, synthesizing required and forbidden rules by architectural layer, running a technical-director gate, and writing the output to docs/architecture/control-manifest.md.

What is the best way to organize architecture constraints by layer for implementation?▼

The best way to organize architecture constraints is grouping extracted rules into foundation, core, feature, and presentation layers. This approach generates per-layer rule counts and applies a technical-director governance gate to ensure implementation readiness.

Does generating a control manifest require engine reference and technical preferences files?▼

Yes, generating a control manifest requires consuming technical preferences and engine reference files to extract naming conventions, performance budgets, deprecated APIs, and current best practices. These sources combine with Accepted ADRs to form complete implementation constraints.

How do I synthesize forbidden patterns and required rules from technical documents?▼

Synthesize forbidden patterns and required rules by reading Accepted ADRs, technical preferences, and engine reference files, then applying a technical-director gate to validate the extracted constraints before writing them into a structured control manifest.