make /task-new always chain into the resolver #28
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/always-implement"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal:
/task-newnever ends with a drafted PR and no resolver pass.Value: med
Effort: 30m
Why
Step 11 made "drafted, not implemented" a reachable end state twice over:
it printed the PR and asked "want to adjust anything?" (an invitation to
stop), and it skipped the
/task-implementchain entirely inimprove-existing mode. Runs kept ending at the spec.
The pipeline's only legal stop is the resolver's code-complete point --
before the test loop and before the first
/task-review./task-orchestratealready auto-runs review + fix (cap 3 passes) andstops only before merge, so nothing downstream needed changing.
Steps
task-newfrontmatter + Overview: state the hand-off as unconditional.line, not a gate; both modes chain; the only skip is running as a
subagent of
/task-implement(loop guard).point at
/task-orchestratefor the auto-run review + fix loop.task-implementStep 1f: the picker's "draft a new task PR" option nowsays spawn, re-probe, resume at Step 2 -- never end the pass at
"drafted".
Notes
Prose-only change across two
SKILL.mdfiles; no scripts touched, sothere is nothing for
tests/to cover.The subagent-of-
/task-implementskip is kept deliberately -- without itthe chain loops
implement -> new -> implement./task-orchestratewas read and left alone: Step 4 already loopsfix-on-branch on
concerns/blockingwithout prompting, and Step 5 isthe intended merge gate.