plan-verifying-execution
Guides judging whether completed execution actually did what the plan said, by checking claims against the repository rather than against the checklist.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- plan-verifying-execution
- description
- Guides judging whether completed execution actually did what the plan said, by checking claims against the repository rather than against the checklist.
- when_to_use
- Use when auditing finished plan execution before archival, or when extending an execution checker's methodology.
- compatibility
- Requires read access to the repository and the ability to re-run its checks.
03 SKILL.md 正文
Verifying Plan Execution
The temporal sibling of validating a draft. The same domains, asked after the fact, against the repository instead of against the text.
Verify Against the Repository, Not the Checklist
A ticked box is a claim. The entire value of this audit is testing claims against what the repository now contains.
Does the file exist at the path the item named? Does the command still pass when re-run? Does the evidence establish the criterion it is filed under, or merely sit next to it?
An audit that reads only delivery.md establishes that the plan is internally consistent — which was never in doubt,
and which a plan can be while describing work that did not happen.
The Two Silent Failures
Scope drift. Work added quietly because it seemed necessary, or dropped quietly because it turned out not to be.
Both are invisible in a checklist where every box is ticked. Compare what was delivered against what prd.md said, not
against what delivery.md recorded.
Evidence that does not establish its claim. A passing test filed under a criterion it does not exercise. A screenshot filed as proof of a behaviour it does not show. These pass a glance and fail on reading.
Gates Must Have Actually Run
A declared gate that never ran is not a passing gate. Check for the evidence record — command, commit, timestamp, result — rather than for the absence of complaints.
A gate that returned findings and was then repaired is fine, and is a different thing from a gate nobody invoked.
Cleanup Is Proven, Not Assumed
Re-list the paths the plan said would be removed. "Cleanup ran" is a claim of the same kind as a ticked box.
Knowledge Capture Is Part of Execution
Every learning must reach a durable owner or be discarded with a reason. An unrouted learnings.md blocks archival —
this is the step most often waived, and the one whose omission costs the most later, because the discovery is lost at
exactly the moment it was cheapest to keep.
Blocking Is the Default
Report what is unresolved plainly rather than passing with a caveat. A caveat in a verdict is read as a pass by everyone who skims it.
04 同仓库更多 Skills
writing-browser-e2e-tests
Guides writing browser end-to-end tests that find elements as users do, wait on what the action produced, keep page knowledge in page objects, organize one feature per file, and run scenario-backed suites from generated specs.
usability-heuristic-evaluation
Guides judging a running interface as a first-time user would, without its specifications: citing a named principle for every finding, walking each task step, reading labels and addresses for scent, and rating severity.
tooling-nx
Guides Nx workspace work under the Nx standard: selecting projects by the graph, adding a target only where a capability exists, tracing a stale cached pass to its missing input, and answering a module-boundary finding.
programming-typescript
Guides the procedure for writing or changing TypeScript: loading the TypeScript standard first, driving each increment test-first, finding which rule a decision falls under, and confirming the gates before handing off.
programming-shell
Guides shell work under the shell standards: checking the declared dialect first, deciding whether logic belongs in shell at all, tracing where exit-on-error does not reach, and testing the script as its callers run it.
programming-javascript
Guides JavaScript work under the JavaScript standard: confirming the file is type-checked, typing through JSDoc, validating input the checker cannot see, and noticing floating promises and swallowed errors before handing off.