create-control-manifest
This skill transforms accepted architecture decision records into a single, layer-organized reference guide that tells programmers exactly what to do and what to avoid. It pulls rules from ADRs, technical preferences, and engine docs, then surfaces them by Foundation, Core, Feature, and Presentation layers—answering "what do I do?" faster than reading the reasoning behind each decision.
Create Control Manifest extracts architecture decisions into a flat, actionable rules sheet organized by layer for programmers.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-21
Create Control Manifest extracts architecture decisions into a flat, actionable rules sheet organized by layer for programmers. This skill transforms accepted architecture decision records into a single, layer-organized reference guide that tells programmers exactly what to do and what to avoid. It pulls rules from ADRs, technical preferences, and engine docs, then surfaces them by Foundation, Core, Feature, and Presentation layers—answering "what do I do?" faster than reading the reasoning behind each decision.
Use it when
- create-control-manifest extracts architecture decisions into a flat, actionable rules sheet for programmers.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
Donchitos/Claude-Code-Game-Studios/create-control-manifest · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does create-control-manifest do?
create-control-manifest transforms accepted architecture decision records into a single, layer-organized reference guide that tells programmers exactly what to do and what to avoid. It pulls rules from ADRs, technical preferences, and engine docs, then surfaces them by Foundation, Core, Feature, and Presentation layers—answering "what do I do?" faster than reading the reasoning behind each decision.
How do I generate a control manifest from ADRs?
create-control-manifest extracts architecture decisions into a flat, actionable rules sheet for programmers. Feed it your accepted ADRs and technical preferences, and it generates do's and don'ts organized by architectural layer, converting each decision into enforceable coding guidelines you can reference immediately.
Can create-control-manifest create layer-by-layer coding rules?
Yes. create-control-manifest organizes all extracted rules by Foundation, Core, Feature, and Presentation layers. Each layer gets its own do's and don'ts, so programmers know exactly which constraints apply at their level without wading through unrelated decisions.
Does create-control-manifest include performance budgets?
create-control-manifest creates a quick-reference manifest that includes performance budgets and forbidden APIs pulled from your ADRs. It surfaces these constraints alongside coding guidelines so developers see both what they must do and what they must never do in one place.
What happens when ADRs change or get accepted?
create-control-manifest can regenerate the control manifest whenever ADRs change or are accepted. Run it again with your updated decision records, and it rebuilds the rules sheet to keep your programmer guidelines in sync with your latest architectural choices.
Is create-control-manifest open source?
Yes, create-control-manifest is released under the MIT license, so you can use, modify, and distribute it freely within the terms of that license.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Create Control Manifest
The Control Manifest is a flat, actionable rules sheet for programmers. It answers "what do I do?" and "what must I never do?" — organized by architectural layer, extracted from all Accepted ADRs, technical preferences, and engine reference docs. Where ADRs explain why, the manifest tells you what.
Output: docs/architecture/control-manifest.md
When to run: After /architecture-review passes and ADRs are in Accepted
status. Re-run whenever new ADRs are accepted or existing ADRs are revised.
1. Load All Inputs
ADRs
- Glob
docs/architecture/adr-*.mdand read every file - Filter to only Accepted ADRs (Status: Accepted)
(truncated - see the full file via the links below)
File tree — 1 file
.claude/skills/create-control-manifest/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Extract architecture decisions into a flat, actionable rules sheet for programmers”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill guides you through authoring Architecture Decision Records (ADRs) that capture major technical choices with full context. It validates decisions against existing architectural stances, engine compatibility, and GDD requirements, then generates a structured record with status, dependencies, and consequences tracked. Use it to retrofit missing sections into existing ADRs or create new ones from scratch.
Create Epics transforms approved design documents and architecture into named, bounded epics—one per architectural module. Each epic defines scope, identifies governing architecture decisions, flags engine risk, and traces requirements to decision coverage. Run this skill once per development layer after control manifest and architecture review pass; follow each epic with /create-stories to decompose into implementable work.
When a game design document is revised, architectural decisions built on it may become stale. This skill reads the changed GDD, compares it against all architecture decision records, and produces a detailed impact report classifying each ADR as still valid, needing review, or likely superseded. It then guides you through resolution decisions and updates your traceability index.
This skill captures architectural decisions made during coding sessions as structured ADR documents that live alongside your codebase. It detects decision moments, gathers context and alternatives, and maintains a searchable log so future developers understand the reasoning behind your architecture.
ADR Skill helps teams document architecture decisions as executable specifications for coding agents. It guides you through a four-phase workflow—scanning existing decisions, capturing intent through structured questions, drafting the record with implementation details, and validating against an agent-readiness checklist. Built for codebases where decisions must be explicit, measurable, and actionable.
Prod Activation Plan materializes multi-phase initiatives using a battle-tested folder structure: a single index file at the root, one folder per phase, and one detailed file per item. Each item captures owner, dependencies, pending decisions, and suggested agent team, ensuring every activation or rollout stays organized and unblocked.
More skills Adr (NOASSERTION) · Diagram Design (NOASSERTION)