verify-before-plan

Solid

Verify orchestrator premises (file counts, build state, artefact presence) before dispatching parallel subagents. Use when a wave's briefs cite a number, path, or behaviour not yet checked.

Data & Documents 48 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Verify Before Plan A premise is anything the orchestrator's plan asserts about the world without having looked: "there are 41 SKILL.md files that need editing," "the deprecated endpoint still has callers," "build is green on main," "the agent must rewrite the manifest." Before a wave of parallel subagents fans out against that premise, **verify it with a small read-only probe**. A wrong premise propagates to every brief in the wave and wastes an entire wave's worth of work — restarting is the only honest salvage. ## When to Use This Skill | Use this skill when... | Skip when... | |---|---| | About to dispatch ≥2 parallel agents whose briefs cite a number, state, or path | Single-agent delegation — verify inline | | The premise was carried in from an earlier message and not re-checked this session | The premise was produced by a tool call earlier in this same session | | The user's report describes a symptom; the plan cites a cause | Waves entirely independent of repo state (e.g. brainstorming) | | The plan assumes a tool/library/agent does X based on its name or docs | The behaviour is covered by a passing test the wave will re-run | | The plan inherits a premise from another agent's return contract | The return contract already cites file:line evidence for the premise | This skill sits **before** `parallel-agent-dispatch` in the dispatch sequence. `parallel-agent-dispatch` covers the contract; this skill covers the assumption the contract is built on. ## The Verificat...

Details

Author
laurigates
Repository
laurigates/claude-plugins
Created
7 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ce-verify

Verify a plan's implemented features work together — whole-suite regression, journey walks, durable-noun revisits, bridge retirement, dependency-manifest integrity, stakeholder acceptance — and produce the handover report. Triggers: verify/integration-test/pre-handover-check a plan. Asks DOES IT BEHAVE (a gate); for code quality use /ce-review.

0 Updated 4 days ago
relusion
AI & Automation Solid

proof-verify

Plan-based verification - freeze acceptance criteria before building, then verify after with an independent fresh-context agent (the builder must not verify their own work). Use when - "verify against plan", "proof check", "independent review", "check the implementation", or confirming a feature built from a plan meets spec. Do NOT use for quick one-off checks with no plan, or for letting the builder self-verify.

138 Updated yesterday
AnastasiyaW
Code & Development Solid

unikit-verify

Verify a completed implementation against the feature plan in .unikit/code/plans/. Confirms every planned task was fully implemented and nothing was forgotten, the code compiles, the tests pass, and {{engine_name}}-specific conventions are followed (per ENGINE_RULES.md). Run this after /unikit-implement finishes, or whenever the user wants to confirm the work is complete and correct against the plan, e.g. "verify", "verify the implementation", "check the work", "did we miss anything", "did we implement everything", "is the plan fully done", "make sure nothing was forgotten", "does it build and pass tests". This checks plan completeness and build/test health — for code-quality, bug, and security review use the review skill instead.

16 Updated 5 days ago
NintendaDev