create-control-manifest

Generate a control manifest from ADRs, technical preferences, and engine references.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill create-control-manifest-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/create-control-manifest
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill create-control-manifest-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Control Manifest provides a flat, actionable rules sheet for programmers, consolidating ADR decisions, technical preferences, and engine references into a single reference document to guide implementation and governance.

Core Features & Use Cases

  • Input aggregation: loads accepted ADRs, tech preferences, and engine references to form the rule set.
  • Rule extraction: converts ADR content into concrete required patterns, forbidden approaches, performance guardrails, and engine API constraints across multiple architectural layers.
  • Global governance: applies naming conventions, performance budgets, and forbidden APIs globally, ensuring consistency across projects.
  • Use Case: a software team uses the manifest to align developers on architecture decisions during feature work and to accelerate onboarding for new engineers.
  • Output: produces docs/architecture/control-manifest.md describing rules for reference and automation.

Quick Start

Run the manifest generator after architecture review passes to generate the control manifest.

Frequently Asked Questions about create-control-manifest

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

FAQPage Schema
How do I generate a control manifest from accepted ADRs?

To generate a control manifest from ADRs, run the manifest generator after architecture review passes. It aggregates accepted ADRs, technical preferences, and engine references to produce a flat rules sheet at docs/architecture/control-manifest.md.

What is a control manifest in software architecture?

A control manifest is a flat, actionable rules sheet consolidating ADR decisions, technical preferences, and engine references into a single document to guide implementation and governance across all architectural layers.

How do I extract required patterns and forbidden approaches from architecture decisions?

Extract required patterns and forbidden approaches from architecture decisions by loading accepted ADRs into the manifest generator, which converts them into concrete rules including performance guardrails and engine API constraints.

When do I need to generate a control manifest for my project?

You need to generate a control manifest when your ADRs are accepted and architecture review is complete, ensuring developers have a consolidated reference document for required rules, forbidden approaches, and global naming conventions.

Can I apply global naming conventions and performance budgets across multiple architectural layers?

Yes, you can apply global naming conventions and performance budgets across multiple architectural layers. The manifest generator extracts global constraints from ADRs to ensure consistency across projects and layers.

What limitations exist when generating a control manifest from ADRs?

The control manifest generation applies only to architectures where ADRs are Accepted and architecture review is complete. ADRs not yet accepted or lacking technical preferences will not be fully represented in the final rules sheet.