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: 80/100
Skill Content
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
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.
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.
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.