create-control-manifest

Parse accepted ADRs and technical documents into a layered control manifest.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between high-level architectural decisions (ADRs) and daily coding tasks by distilling complex design documents into a flat, actionable rules sheet for programmers.

Core Features & Use Cases

  • Automated Rule Extraction: Automatically aggregates requirements, forbidden patterns, and performance guardrails from accepted ADRs and technical documentation.
  • Layered Organization: Categorizes rules by architectural layer (Foundation, Core, Feature, Presentation) to ensure developers have context-specific guidance.
  • Use Case: After finalizing a major architectural change, use this Skill to update the team's control manifest, ensuring all developers are immediately aware of new constraints and deprecated APIs.

Quick Start

Run the create-control-manifest skill to generate the latest architectural rules sheet based on all currently 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 actionable rules from Architecture Decision Records for developers?▼

To extract actionable rules from Architecture Decision Records, you can parse accepted ADRs and technical preference documents to distill complex design decisions into a flat, actionable rules sheet for programmers.

What is a control manifest in software architecture governance?▼

A control manifest in software architecture governance is a consolidated, actionable rules sheet that categorizes architectural constraints by Foundation, Core, Feature, and Presentation layers to guide daily coding tasks.

How do I enforce architectural standards across different application layers?▼

You can enforce architectural standards across application layers by generating a control manifest that categorizes extracted requirements, forbidden patterns, and performance guardrails into Foundation, Core, Feature, and Presentation contexts.

Does generating an architectural rules sheet require access to the documentation directory?▼

Generating an architectural rules sheet requires access to the repository's documentation directory to extract and classify implementation guidelines, accepted ADRs, and performance constraints.

When should I update my software development team's control manifest?▼

You should update your software development team's control manifest after finalizing a major architectural change to ensure all developers are immediately aware of new constraints and deprecated APIs.