ship-verify
Use when a feature build is complete and needs verification against acceptance criteria and adversarial testing
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when a feature build is complete and needs verification against acceptance criteria and adversarial testing
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a feature plan has been verified and is ready for implementation — executes tasks with atomic commits
Use when you want to auto-run all remaining Ship steps for a feature without manual step-by-step invocation
Use when a feature has been brainstormed and needs a detailed implementation plan with tasks
Use when a brainstormed feature needs architectural decisions — presents 2-3 approaches for user to choose before planning
Use when a plan has been created and needs independent verification against codebase patterns before building
Use when beginning new feature work, adding functionality, or fixing a bug — runs intensive brainstorming to capture requirements before planning
| name | ship:verify |
| description | Use when a feature build is complete and needs verification against acceptance criteria and adversarial testing |
| effort | high |
| allowed-tools | Read, Agent, Glob, Edit, Bash |
| argument-hint | [feature-name] |
Verify the active feature's implementation.
Feature state is injected by hooks at session start and after compaction — check conversation context for "SHIP ACTIVE FEATURES" or "SHIP FEATURE STATE" blocks first.
$ARGUMENTS is provided, use it as the feature namebuilt.planning/features/*/CONTEXT.mdUse the Agent tool to invoke the ship-verifier agent. It is the single post-build quality gate: it verifies every acceptance criterion against the running code, hunts bugs with adversarial tests, scans for anti-patterns, and writes VERIFY.md.
Verify feature: {name}
Read .planning/features/{name}/CONTEXT.md and PLAN.md, then follow your verification
instructions: verify acceptance criteria with the gate function, write and run
adversarial tests for the relevant risk categories, scan the changed files for
anti-patterns, and write VERIFY.md. Critical or high bugs and any failing criterion
block a PASS.
Extract the verify_result JSON block from the agent's output and read .planning/features/{name}/VERIFY.md for the full report. Display:
## VERIFICATION COMPLETE
Feature: {result.feature}
Status: {result.status}
Criteria: {result.criteria_passed} / {result.criteria_total} passed ({result.criteria_inconclusive} inconclusive)
Tests: {result.tests_written} written, {result.tests_passed} passed
Bugs: {by severity from result.bugs}
Anti-patterns: {result.anti_patterns} found
[If result.gaps is non-empty:]
Gaps:
- {each item from result.gaps}
[If result.status is "PASS" or "INCONCLUSIVE":] Next: /ship:finish
[If result.status is "FAIL":] Next: /ship:build (fix tasks added to PLAN.md)
$ARGUMENTS