Create Control Manifest
Builds a short list of must-do and never-do coding rules per system from accepted ADRs.
Install
npx skills add Donchitos/Claude-Code-Game-Studios --skill create-control-manifest -g -a claude-code -y- Repository
- Donchitos/Claude-Code-Game-Studios32.1k
- Category
- Engineering
- Updated
- 17d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Builds a short list of must-do and never-do coding rules per system from accepted ADRs. Use when the user wants programmer rules or a cheat sheet from the ADRs, or needs it regenerated after ADR changes.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,review_gate,automation
Resolved above, use as-is; --review overrides review_mode for this run. No
block → defaults in .claude/docs/config-resolution.md.
Ask with the question tool. Without one, list the options numbered and end your turn to wait. A skipped or dismissed question is not an answer: ask again in plain text.
Create Control Manifest
The control manifest is a flat rules sheet for programmers: what to do and what never to do, by architectural layer, taken from the Accepted ADRs, the project's technical preferences and the engine reference docs. The ADRs say why; the manifest says what.
Writes: docs/architecture/control-manifest.md, after the user's yes.
When: after /architecture-review passes and the ADRs are Accepted. Run it
again whenever an ADR is accepted or revised.
Asks follow .claude/docs/automation-modes.md (collaborative always asks, guided
asks on major choices, autonomous logs and goes on; automation_always_ask
categories always ask).
Phase 1: Load the inputs
ADRs
bash .claude/scripts/adr-status.sh reads every docs/architecture/adr-*.md in one
pass: the counts first (adrs, then accepted, proposed, deprecated,
superseded, unfilled, other, no_status), then one row per ADR with its
status and layer. Establish the denominator first: decide from the counts, before
reading any ADR:
