delivery-baseline-audit
Installation
SKILL.md
Delivery Baseline Audit
Verify that the promised deliverables actually exist relative to where the work started.
Use When
- the task names files, features, screens, commands, or other concrete deliverables;
- the implementation ran through multiple phases or retries;
- the working tree may contain staged, unstaged, or untracked work that matters;
- "agent said done" is not enough evidence.
Core Rules
- Compare against the starting baseline, not just the latest transcript claim.
- Check the whole working tree, not only committed diffs.
- Re-run final mandatory commands once at the end for cross-phase regressions.
- Treat missing deliverables as a gap even if the narrative sounds complete.