Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Prove It Works
Verify every task output by checking the real thing directly. Do not infer from proxies, self-reports, or "it compiles."
**Why:** Unverified work has unknown correctness. Indirect verification (file mtimes, output freshness, agent self-reports, cached screenshots) feels cheaper than direct observation. Acting on a wrong inference costs far more than checking the source.
**Pattern:** After completing any task, ask: "how do I prove this actually works?"
Check the real thing, not a proxy:
- Check process liveness directly, not indirectly through derived state
- Read the actual value, not a cached or derived representation
- When verification fails, suspect the observation method before suspecting the system
Code and features:
1. Build it (necessary but not sufficient)
2. Run it and exercise the actual feature path
3. Check the full chain: does data flow from input to output?
4. For integrations, test the full communication path end-to-end
Delegation: trust artifacts, not self-reports.
…
The line at the top of this page pins the label git:20260827.04830a9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_kily5el7ltqu3szf
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-prove-it-works
GET https://markdownregistry.com/api/v1/blob/124cebf0527fb24bd37be21dbbf4447f9ddce5c058872cfce047e043bbf70bfd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
painhardcore/pstack · .opencode/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
painhardcore/pstack · .opencode/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
painhardcore/pstack · .opencode/skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
painhardcore/pstack · .opencode/skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
painhardcore/pstack · .opencode/skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
painhardcore/pstack · .opencode/skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
painhardcore/pstack · .opencode/skills/principle-boundary-discipline/SKILL.md · Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI…
cursor/plugins · harness/pstack/claude-code/skills/principle-prove-it-works/SKILL.md · Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the…
cursor/plugins · pstack/skills/principle-prove-it-works/SKILL.md · Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-prove-it-works/SKILL.md · Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the…
backnotprop/pstack · skills/principle-prove-it-works/SKILL.md · Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/prove-it-works/SKILL.md · Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the…
creedants/pstack-t3 · skills/principle-prove-it-works/SKILL.md · Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the…
arjitj2/open-pstack · plugins/pstack/skills/principle-prove-it-works/SKILL.md · Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the…
shiwenbin1617/pstack · skills/principle-prove-it-works/SKILL.md · Choose evidence that verifies the changed behavior and supports the completion claim.