verify-before-plan
SolidVerify 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.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- laurigates
- Repository
- laurigates/claude-plugins
- Created
- 8 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
verification-planning
Plans how to prove a change works or broke nothing: frames the claim, designs an evidence path from the system itself, and requires every check to be able to fail.
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 /core-engineering:ce-review.
verify-plan
Verify implementation plans before execution with a single Opus subagent driven by a structured six-section checklist. Use when you have a written plan (from /bdk:create-plan or manual) and want to check it works before writing code.