القائمة
Use when about to claim work complete, fixed, passing, or ready, including before moving to the next planned task.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when following the Super Compound BRD -> PRD -> FSD -> GOAL -> IMPLEMENTATION -> VERIFICATION delivery path, artifact traceability, FSD authority, optional ADR handling, zero context bloat issue slicing, or OPEN-* stop conditions.
Use when an approved FSD goal or lightweight issue pointer is ready for implementation.
Use when multi-component work needs cross-component verification of API contracts, data flow, events, auth, config, UI, background jobs, or tests.
Use when /sc-plan needs FSD GOAL-* packets turned into lightweight issue pointers, local Markdown Kanban boards, blocker DAGs, or multi-agent task contracts.
Use when a plan or issue board has 2+ independent execution streams whose time saving exceeds coordination overhead. Dispatches agents in isolated git worktrees only after required delivery gates pass.
Use when an FSD and goal issue board need requirement coverage, goal quality, dependency DAG, sizing, and verification validated before execution.
| name | verification-before-completion |
| description | Use when about to claim work complete, fixed, passing, or ready, including before moving to the next planned task. |
Evidence precedes every success claim. Confidence, a changed diff, and another agent's report are not evidence.
Apply this gate before any completion or satisfaction wording, task transition, commit, push, PR claim, or delegation that assumes preceding work succeeded.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
No executable proof available? Use an explicit requirement checklist and direct artifact inspection; disclose residual uncertainty. Never convert missing evidence into success wording.
| Thought | Required response |
|---|---|
| "It should work" / "I'm confident" | Run the proving check. |
| "A partial suite is enough" | Run the full relevant check or narrow the claim. |
| "The subagent said it passed" | Verify independently. |
| "The linter passed, so the build/tests pass" | Each claim needs its own evidence. |
| "Different wording avoids the rule" | Implication of success is still a claim. |
executing-plans invokes this before task completion.test-driven-development supplies red-green evidence.systematic-debugging supplies symptom and regression evidence.code-review verifies findings before reporting them.gap-closure re-runs the original verification.state-management records verified status only after this gate.