skills.rest
striderZA
striderZACOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-control-manifest

Extract ADR constraints into an architecture control manifest.

72|7|Updated Apr 29, 2026
Search Tags:#architecture#adr#documentation generation#rules extraction#engine compatibility#performance guardrails#technical director gate
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill create-control-manifest-striderza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-control-manifest
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/create-control-manifest
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill create-control-manifest-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from missing architectural constraints by converting accepted ADR decisions, technical preferences, and engine references into a single actionable rules sheet programmers can follow.

Core Features & Use Cases

  • Extracts mandatory and forbidden patterns from all Accepted ADRs, so the resulting document reflects what is required and what must never be done.
  • Captures performance and engine constraints (guardrails, budgets, deprecated or unverified APIs) to reduce implementation risk in the pinned engine version.
  • Organizes rules by architectural layer (Foundation, Core, Feature, Presentation) and includes global naming/performance/library/forbidden API entries for consistent implementation.
  • Writes the manifest to docs/architecture/control-manifest.md and supports regeneration when ADRs change.

Quick Start

Run the skill command to generate and write the control manifest to docs/architecture/control-manifest.md after your ADRs are marked Accepted.

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 programming rules?▼

A control manifest organizes extracted ADR constraints by architectural layer—Foundation, Core, Feature, and Presentation—so programmers receive clear mandatory patterns, forbidden APIs, and performance guardrails for a specific engine version.

How do I generate a control manifest from architecture decision records?▼

You need accepted ADRs marked with an Accepted status, plus technical-preferences and engine reference files documenting forbidden APIs and best practices for the pinned engine version. The Skill reads these to extract constraints before generating the manifest.

Does this ADR rules extraction process work with engine reference docs?▼

The Skill routes the previewed manifest through a TD-MANIFEST director gate based on the technical mode, ensuring technical director approval is integrated into the architecture-review-to-production workflow before writing the final control manifest.

What is the best way to document forbidden APIs and performance guardrails from ADRs?▼

The manifest supports regeneration when ADRs change, allowing teams to re-run the extraction process to produce an updated control manifest that reflects new accepted decisions, revised technical preferences, or updated engine reference documentation.

Related Skills

Explore More Software Engineering Skills→
imclabimclab
1

create-control-manifest

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

Official
Advanced
hernamesbarbarahernamesbarbara

writing-documentation

Generate READMEs, API references, user guides, ADRs, and runbooks from codebases.

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

create-control-manifest

Convert accepted ADRs and engineering guidance into a control manifest.

Community
Advanced
FrancisVargaFrancisVarga

create-control-manifest

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

Community
Advanced