foreman-verify
Headless self-verification gate a Foreman worker runs before it claims an issue is done. Re-run the real commands, read the actual output, and only then write the FOREMAN-SUMMARY — evidence before claims, always. Used inside a foreman-tdd build session; emits no summary of its own.
npx skills add VisionForge-OU/foreman --skill foreman-verify --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# foreman-verify (Adapted from obra/superpowers `verification-before-completion` (MIT) — see NOTICE. Made headless and wired to Foreman's trust boundary: the "claim" you are gating is the foreman-tdd FOREMAN-SUMMARY block and its `evidence` array, and the verification commands are the project's own, run through the `foreman-test` wrapper. Foreman re-runs every command itself regardless, so a dishonest claim is not just wrong — it is rejected and counts as a failed attempt.) You are invoked **inside a foreman-tdd build session**, right before it would claim the slice is complete. Your job is to make that claim *true and evidenced*. You run **headless** and emit **no FOREMAN-SUMMARY** of your own — you populate the evidence the surrounding foreman-tdd run reports. ## The Iron Law ``` NO COMPLETION CLAIM WITHOUT FRESH VERIFICATION EVIDENCE ``` If you have not run the verifying command **in this session** and read its output, you may not claim it passes. "Should pass", "I'm confident", "it worked earlier" are not evidence. ## The gate function For **every** claim the FOREMAN-SUMMARY will make (tests pass, lint clean, typecheck clean, the issue's `acceptance_check` passes, the behaviour
- The Iron Law
- The gate function
- What counts (and what doesn't)
- Output
- Red flags — stop
What does the foreman-verify skill do?
Headless self-verification gate a Foreman worker runs before it claims an issue is done. Re-run the real commands, read the actual output, and only then write the FOREMAN-SUMMARY — evidence before claims, always. Used inside a foreman-tdd build session; emits no summary of its own.
How do I install it?
Run `npx skills add VisionForge-OU/foreman --skill foreman-verify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From VisionForge-OU/foreman, a repository with 421 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.