Run the `verify:` command for a bd issue by its ID (e.g. story-editor-9vm) and report the true exit code — without letting `grep -iv error` or other pipeline tricks mask a failure. Use before `/bd-close <id>` to confirm work is done. User-invocable as `/task-verify <BD_ID>`.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "task-verify" with this command: npx skills add DoctorKomodo/skillsmp-doctorkomodo-doctorkomodo-task-verify
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Bridge from bd → superpowers' subagent-driven-development loop. Claims a bd issue, reads its plan link, picks rules digests by touch-set, then runs the implementer + spec-reviewer + code-quality-reviewer loop with project rules prepended at each dispatch. After the loop reports CLEAN, hands off to `/bd-close-reviewed`. User-invocable as `/bd-execute <BD_ID>`.
Close a bd issue through the project's review gate — typecheck affected workspaces, fan path-matched surface reviewers (security-reviewer, repo-boundary-reviewer), refuse close on BLOCK / FIX_BEFORE_MERGE unless `--override-block "<reason>"` with user ack. Called by `/bd-execute` at end-of-loop, or directly when work didn't go through `/bd-execute`. User-invocable as `/bd-close-reviewed <BD_ID>`.
Record a `plan: <path>` link at the top of a bd issue's notes, preserving existing notes (especially the `verify:` line). Use after `superpowers:writing-plans` lands a plan file, before `/bd-execute`. User-invocable as `/bd-link-plan <BD_ID> <PLAN_PATH>`.
Gate-then-close a bd issue — runs the issue's `verify:` line via pipefail, only calls `bd close` if it exits 0. Use after `/task-verify` to commit a task as done. User-invocable as `/bd-close <BD_ID>`.