Rename issue capture to /iflow-capture; reclaim /iflow-init for harness (#241) - #245
Merged
Conversation
…ss (#241) /iflow-init used to mean "pull this GitHub issue into .issueflows/", which overloaded the word init that already means scaffolding the harness via the CLI. Move that lifecycle step to /iflow-capture so it matches issue-flow agent capture, and make /iflow-init an off-path cold-start/check that guides issue-flow init / update without ever capturing an issue. Lifecycle stage id is now capture (STAGE_INIT kept as a back-compat alias); suggested next command is /iflow-capture. No one-release dual-meaning alias — same stance as the iflow-start → iflow-build rename (#183). Dispatcher, pick, yolo/cycle chains, rules, workflow doc, and modes.simple updated accordingly. Co-authored-by: Cursor <cursoragent@cursor.com>
#247 landed guided setup / novice mode while this PR renamed issue capture to /iflow-capture. Resolve the overlap so the three names stay distinct: /iflow-setup walks environment readiness, /iflow-init only cold-starts the harness, /iflow-capture pulls a GitHub issue. Add iflow-capture to novice mode (it used to live under iflow-init) and retarget leftover /iflow-init-as-capture wording in setup templates, README, and docs. Co-authored-by: Jan Petter Maehlen <jepe@ife.no>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #241
Summary
/iflow-captureis the lifecycle step that pulls a GitHub issue into.issueflows/(matchesissue-flow agent capture)./iflow-initis now off-path harness cold-start / check: guidesissue-flow init/update; never captures issues; never auto-dispatched by/iflow.capture(STAGE_INITkept as a back-compat alias). No one-release dual-meaning alias (same stance asiflow-start→iflow-buildin renaming from start to build #183).Why
/iflow-initmeant "capture this issue", but init already means scaffolding the harness via the CLI. That mismatch is what #241 asked to fix. Nameiflow-thiswas floated in the issue and walked back in a comment; we lockediflow-captureinstead.Test plan
uv run pytest— 646 passed locallyuv run ruff check src/ tests//iflow-cleanup(and note muscle memory: issue pull is nowiflow capture//iflow-capture)Made with Cursor