taskforge-runlisted

Implement a taskforge task against its active Specification and verify it with an independent fresh-context review subagent. Use when a task's readiness is "run", or when the user asks to run, implement, execute, build, or ship a taskforge task that has a specification. Covers the implement-review-retry loop, recorded-and-auditable reviewer isolation, root-cause escalation back to taskforge-refine or taskforge-explore, and scope discipline (out-of-scope discoveries become follow-up tasks). Tasks without an active specification route to taskforge-refine instead.
hashirventhodi/taskforge-skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill hashirventhodi/taskforge-skills

# taskforge-run Implement the active Specification, then submit the work to an independent reviewer in a fresh context. Run finishes a task or escalates it — it never quietly lowers the bar and never expands scope. **Prerequisites**: read `taskforge/CONTRACTS.md` this session; resolve `$SCRIPT`; guard on readiness (`run` required). ## 1. The spec is the whole contract `python3 $SCRIPT show <id>`. The active specification — not the description, not your memory of the conversation — is what you implement and what the reviewer judges. Spec vs description conflict? The spec wins; note the conflict in your report. Record the spec's version; you cite it in artifacts. Check `python3 $SCRIPT budget <id>` if resuming a task with prior rejections. ## 2. Implement Plan briefly; work on an isolated line (branch `taskforge/<task-id>` in a git repo); run the tests. **Scope discipline is binding.** Adjacent problems you notice — flaky tests, dead code, missing validation elsewhere — become `follow_up` entries in your result, described to stand alone. Never extra diff: the reviewer should see nothing the spec didn't ask for. **Upstream discoveries end the attempt immediately** — don't push through a broken contract: * spec ambiguous/contradictory/unimplementable → `signal: escalate_refine`, the defect named precisely; * the approach itself cannot work → `signal: escalate_explore`; * blocked on something only a human can resolve → `signal: block_on_human`. Include artifacts alread