create-control-manifest

Generate control manifests from architecture decisions and technical preferences.

Updated May 16, 2026
One-click install
npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill create-control-manifest-seonghuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/SeongHuni/LightNShadowSurviver/tree/main/GameStudio/codex/skills/create-control-manifest
Command: npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill create-control-manifest-seonghuni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive rules sheets for programmers, ensuring adherence to architecture decisions, technical preferences, and engine reference documentation.

Core Features & Use Cases

  • Extracts Rules from ADRs: Compiles requirements and forbidden approaches from accepted architecture decisions (ADRs).
  • Includes Technical Preferences: Incorporates naming conventions, performance budgets, and approved libraries from technical preferences.
  • Engine Reference Integration: Uses engine reference documentation for API constraints and best practices.
  • Layered Classification: Organizes rules by architectural layers for clear system management.
  • Director Gate Integration: Provides a technical review process by a designated director agent.

Quick Start

Run the create-control-manifest skill 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 architecture decisions and technical preferences?

A control manifest is generated by analyzing accepted architecture decisions, technical preferences, and engine reference documentation to automatically extract rules, classify them by architectural layers, and integrate director gate reviews.

What is the best way to automate rule extraction from ADRs for a programming team?

Automate rule extraction from ADRs by processing accepted architecture decisions to compile requirements and forbidden approaches, then organizing these rules by architectural layers for clear system management.

Do I need established architecture documentation to create a control manifest?

Yes, creating a control manifest is designed for teams with established architecture documentation and coding standards, requiring accepted ADRs, technical preferences, and engine reference documentation as input.

Can I integrate technical review processes into a control manifest?

Technical review processes are integrated into a control manifest through director gate integration, which provides a designated director agent to review the extracted rules and technical preferences.

How does layered classification work when organizing programming rules?

Layered classification in a control manifest organizes extracted rules and technical preferences by architectural layers, ensuring clear system management and separation of concerns for the programming team.

What limitations exist when generating rules from engine reference documentation?

Generating rules from engine reference documentation is limited to extracting API constraints and best practices, requiring the engine references to be established and accepted prior to control manifest generation.