work-state-and-delivery
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.