Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/create-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Passed 8 of 14 test cases with the skill, and 5 of 14 without it.
and 2 more in the full report
5 fixed8 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our project config file project.yaml specifies naming conventions for classes and variables, but the key for signal naming is missing. Where should signal naming conventions be retrieved from?
| Checked | Without skill | With skill |
|---|---|---|
| Retrieves missing configuration values from technical-preferences.md. | Missed | Passed |
The instructions your model reads when the skill loads.
!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.
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).
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:
| Result | Meaning | Action |
|---|---|---|
N matches, some read Accepted | Normal. | 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. |
test cases passed, vs 5 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.