Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

create-control-manifest

Flat must-do/never-do rules sheet per system and layer, extracted from Accepted ADRs. ADRs explain why; this is actionable.

HYClub · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add HYClub/deepseek-harness-game-studios --skill create-control-manifest

About this skill


name: create-control-manifest description: "Flat must-do/never-do rules sheet per system and layer, extracted from Accepted ADRs. ADRs explain why; this is actionable." argument-hint: "[update — regenerate from current ADRs] [--review full|lean|solo]" user-invocable: true allowed-tools: Read, Glob, Grep, Write, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/create-control-manifest/../../hooks/yaml-helper.sh" resolve_config *) model: sonnet

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation

Resolved above — use as-is; --review overrides review_mode for this run. No block → defaults in .claude/docs/config-resolution.md.

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.


Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

1. Load All Inputs

ADRs

Establish the denominator first. Glob docs/architecture/adr-*.md. Call the count N. If N is 0: "No ADRs found — run /architecture-decision before building a control manifest." Stop.

Resolve status without reading the ADRs — the filter must precede the read, not follow it:

Grep pattern="^## Status" glob="docs/architecture/adr-*.md" output_mode="content" -A 3

Interpret against N:

ResultMeaningAction
N matches, some read AcceptedNormal.The Accepted set is A; proceed with A. Name every ADR left out, with its status, in the Phase 4 preview — the user approves a manifest knowing what it does not cover.
N matches, none AcceptedGenuinely no Accepted ADRs."[N] ADRs found, none Accepted. A manifest built from Proposed ADRs would encode decisions that may still change." Ask whether to proceed with Proposed or stop. Do not silently emit an empty manifest.
0 matches, N > 0Malformed ADRs — not an empty Accepted set. ## Status is BLOCKING-if-missing."[N] ADRs found, none has a ## Status section — acceptance cannot be determined. Run /architecture-decision retrofit [file] on each." Stop. Do not treat all ADRs as Accepted; do not emit a manifest.
  • Note the ADR number and title for every rule sourced.

Project Config

  • Read naming.* and performance.* from project.yaml; for any key absent or empty, fall back to .claude/docs/technical-preferences.md
  • Read approved libraries/addons and forbidden patterns from .claude/docs/technical-preferences.md (not migrated to project.yaml)

Engine Reference

  • Read docs/engine-reference/[engine]/VERSION.md for engine + version
  • Read docs/engine-reference/[engine]/deprecated-apis.md — these become forbidden API entries
  • Read docs/engine-reference/[engine]/current-best-practices.md if it exists

Existing Artifacts

  • Glob docs/architecture/control-manifest.md (present → this run is a regeneration; Read it before the Phase 5 write, which overwrites it) and production/epics/*/EPIC.md (present → epics exist). Phase 6 picks its next step from both.

Report: "Loaded [N] Accepted ADRs, engine: [name + version]."


2. Extract Rules from Each ADR

Read only these four sections per Accepted ADR — not the whole file. Context, Consequences, Migration Plan and Validation Criteria explain why a decision was made; the manifest records what to do, so they are not needed here:

Grep pattern="^## (Decision|Alternatives Considered|Performance Implications|Engine Compatibility)" glob="docs/architecture/adr-*.md" output_mode="content" -A 30

Filter the results to the Accepted set A resolved above. If a section is absent for a given ADR, note it per ADR and continue; if a section is absent across all of A, report "No Accepted ADR contains a [section] section — the manifest's [category] rules will be empty. Verify this is intended." Escalate to a full read of one ADR only when its scanned sections cross-reference material outside them (e.g. a Decision that says "subject to the constraints in Context").

For each Accepted ADR, extract:

Required Patterns (from the ## Decision section)

  • Every "must", "should", "required to", "always" statement in the Decision body — including any ### Implementation Guidelines sub-heading when the ADR has one (newer ADRs emit it; older ones state mandates directly in ## Decision). Never scan for ### Implementation Guidelines alone — it is absent from many skill-authored ADRs, and scanning for it yields an empty Required Patterns section on a manifest that should have been full.
  • Every specific pattern or approach mandated

Forbidden Approaches (from "Alternatives Considered" sections)

  • Every alternative that was explicitly rejected — why it was rejected becomes the rule ("never use X because Y")
  • Any anti-patterns explicitly called out

Performance Guardrails (from "Performance Implications" section)

  • Budget constraints: "max N ms per frame for this system"
  • Memory limits: "this system must not exceed N MB"

Engine API Constraints (from "Engine Compatibility" section)

  • Post-cutoff APIs that require verification
  • Verified behaviours that differ from default LLM assumptions
  • API fields or methods that behave differently in the pinned engine version

Layer Classification

Classify each rule by the architectural layer of the system it governs:

  • Foundation: Scene managemen
Read the complete source ↗