Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
SkillScore91Maintained
Automatic
◆Project Management pack
Last verified 9/2/2026
What it changes
Passed 19 of 21 test cases with the skill, and 9 of 21 without it.
Without skill41%
With skill91%
Checks it passed that the model alone missed
requires updating execution-plan status third
mandates exact-path staging to define commit scope
requires updating work-state and acceptance second
and 10 more in the full report
11 fixed9 passed either way2 still failing0 broke
Pass-rate lift
+50 pp
Tokens
-2%
Agent turns
0%
Response time
-32%
Model gemini-3.6-flashMeasured 9/2/2026v120 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
I am setting up a fresh project and want to figure out where our design specs, task states, and release proofs should go so we avoid redundant trackers. Output a guide detailing the mapped surfaces like design and commit policy, the specific source-of-truth responsibilities, how updates should couple with commits, criteria for task acceptance, required delivery evidence, and the redaction and skip policy.
What was checked, without and with the skill
Checked
Without skill
With skill
mandates exact-path staging to define commit scope
Missed
Passed
requires that active tasks must have executable acceptance criteria
Passed
Passed
assigns exactly one authoritative owner for each kind of truth without overlap
Passed
Passed
case-02 · gemini-3.6-flash · 9/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md91 lines3 files
Work State And Delivery
Overview
Keep intent, current work state, acceptance criteria, and delivery evidence connected without creating duplicate sources of truth.
This optional governance skill combines planning surfaces and delivery ledgers because they meet at task-to-change traceability. It also owns repository commit-coupling policy, but it should not load for an ordinary commit that already follows clear repository rules. For shared harness terms, see ../../references/harness-patterns.md; when governance surfaces are missing, use references/build-when-missing.md; for delivery, skip, artifact, and commit rules, use references/delivery-and-commit-policy.md.
When To Use
The user asks where requirements, design decisions, tasks, acceptance criteria, or execution plans should live.
A repository needs a task board, external-tracker mapping, delivery record, handoff note, or review evidence policy.
Design docs, task state, ledgers, reviews, and commits duplicate or contradict each other.
The user asks to design commit coupling, exact-path staging, task-state updates, or delivery-artifact policy for the repository.
Do not use this skill solely for git status, a read-only diff, or a normal commit when the repository already defines those rules.
Inputs Needed
Current requirement or delivery goal.
Existing design docs, issue tracker or task file, execution plans, review template, ledger, and commit policy.
Then: Assign one owner for each kind of truth and define update, coupling, skip, and redaction rules.
Finally: Output the minimum governance changes, acceptance criteria, and delivery evidence required for the repository profile.
Step-by-Step Process
Search for design docs, tasks.md, issue references, execution plans, review templates, ledgers, release notes, and commit guidance.
Map each existing surface by responsibility rather than filename: design explains why and how; work state owns current status and acceptance; an execution plan coordinates complex work; delivery evidence records what changed and what was proved.
If a required role is missing, bootstrap only the minimum surface from references/build-when-missing.md; do not add a ledger or repo-local task file when an external system already satisfies the role.
Define update order: design decision first, work-state and acceptance second, execution-plan status third, delivery evidence after validation.
When a change completes, changes, or invalidates a tracked task, include its task-state update in the same logical commit or authoritative external-tracker update.
Define exact-path staging, validation evidence, artifact identity, and explicit skip rules in repository guidance; avoid a standalone commit skill for routine execution.
Keep delivery records concise and evidence-oriented; reference prompts or goals, changes, validation, artifacts, risks, tasks, reviews, and commits without storing private transcripts.