Summary
Add a /ck:converge command (or --until-approved flag on /ck:make) that runs the full build-verify-fix cycle autonomously without requiring manual re-invocation between phases.
Current workflow (requires manual intervention)
/ck:make # runs unattended ✓
# ← must return to screen
/ck:check # runs once, produces APPROVE/REVISE/REJECT
# ← if REVISE, must manually trigger again
/ck:make # re-runs unattended ✓
/ck:check # second pass
The user must monitor for completion and re-trigger the cycle manually on REVISE verdicts.
Proposed: /ck:converge
/ck:converge --max-cycles 3
Behaviour:
- Run the build loop to completion
- Run the check phase
- If verdict is APPROVE → done
- If verdict is REVISE → go to step 1 (up to
--max-cycles)
- If verdict is REJECT or max-cycles hit → stop and report
The implementation should handle verdict detection robustly — including cases where the verdict is expressed in varied phrasing rather than an exact keyword match.
Why this matters
A full build session requires manual re-triggers over a multi-hour window. With /ck:converge, the entire cycle runs in a single unattended session from start through approval.
Alternative
Add --until-approved flag to existing /ck:make:
/ck:make --until-approved --max-cycles 3
Summary
Add a
/ck:convergecommand (or--until-approvedflag on/ck:make) that runs the full build-verify-fix cycle autonomously without requiring manual re-invocation between phases.Current workflow (requires manual intervention)
The user must monitor for completion and re-trigger the cycle manually on REVISE verdicts.
Proposed: /ck:converge
Behaviour:
--max-cycles)The implementation should handle verdict detection robustly — including cases where the verdict is expressed in varied phrasing rather than an exact keyword match.
Why this matters
A full build session requires manual re-triggers over a multi-hour window. With
/ck:converge, the entire cycle runs in a single unattended session from start through approval.Alternative
Add
--until-approvedflag to existing/ck:make: