Expand issue-flow workflow with additional slash commands (#39)#41
Merged
jepegit merged 3 commits intoApr 19, 2026
Merged
Conversation
- Introduced four new commands: `/issue-plan`, `/issue-pause`, `/issue-cleanup`, and `/issue-yolo` to streamline the issue management process. - Updated `/issue-close` to delegate post-merge branch hygiene to `/issue-cleanup`. - Implemented `/iflow` as a smart dispatcher to automatically route to the appropriate command based on the current issue state. - Enhanced documentation in `HISTORY.md` to reflect these changes and provide clear guidance on the new command functionalities. This update improves the overall workflow efficiency and user experience in managing issues.
…tions - Revised the documentation to include new commands: `/issue-plan`, `/issue-pause`, `/issue-cleanup`, and `/issue-yolo`. - Updated the command sequence for issue management to enhance clarity and usability. - Added descriptions for the new commands and their functionalities, including the smart dispatcher `/iflow`. - Improved overall structure and readability of the README to guide users through the issue-flow lifecycle more effectively.
Issue #39 is fully resolved. Move issue39_original.md and issue39_status.md from .issueflows/01-current-issues to .issueflows/03-solved-issues per the workflow rule that only the active focus issue lives in 01-. Made-with: Cursor
6 tasks
jepegit
deleted the
39-expand-issue-flow-workflow-with-additional-slash-commands
branch
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
1 participant
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.
Summary
Closes #39.
Expands the
issue-flowlifecycle from three commands (/issue-init,/issue-start,/issue-close) to eight, and adds a smart dispatcher so users don't have to remember the new surface.New commands and skills
/issue-plan— writesissue<N>_plan.md(Goal / Constraints / Approach / Files to touch / Test strategy / Open questions) and stops for user confirmation before any implementation./issue-pause— parks work in.issueflows/02-partly-solved-issues/with a Remaining work note; offers a consolidated WIP-commit + switch-to-default prompt./issue-cleanup— owns post-merge branch hygiene: detects merged PR, switches to default,git pull --ff-only,git fetch --prune, andgit branch -don merged local branches (single consolidated confirm; never-D)./issue-yolo— all-in-one chain (init → plan → start → close) for small, low-risk issues, with up-front safeguards (no default branch, clean tree, passing tests, single consolidated confirm)./iflow— smart dispatcher. Inspects the focus issue (branch-derivedNis authoritative; else single group in01-; else asks) and dispatches to the right linear-flow command based on which files exist and whether the status file is marked- [x] Done. Warns when the focus issue is archived so/issue-init's guard is expected. Forwards trailing args verbatim. Never auto-dispatches to/issue-pause,/issue-cleanup, or/issue-yolo.issueflow-iflow,issueflow-issue-plan,issueflow-issue-pause,issueflow-issue-cleanup,issueflow-issue-yolo).Breaking changes (strict migration)
/issue-startno longer plans. It readsissue<N>_plan.mdand, when missing, offers three options (run/issue-plannow, proceed without a plan and note it in the status file, or abort)./issue-closeno longer deletes branches. Step 7 now points users at/issue-cleanupafter the PR merges.Other changes
TEMPLATE_MANIFESTgrew from 9 to 19 entries; in-tree scaffold regenerated viauv run issue-flow update.docs/cursor-issue-workflow.mdrewritten: new 0. /iflow section, updated end-to-end diagram, expanded command and skill tables, per-command sections for every new command.rules/issueflow-rules.mdcgains a Command lifecycle section with a/iflowone-liner at the top.README.mdrefreshed to match the new scaffold tree, commands, and skills.HISTORY.md[Unreleased]bullet covers the new commands, the two breaking migrations, and the/iflowdispatcher (including the authoritative branch-derived-Nrule).Test plan
uv run pytest— 43 passed (10 new tests covering the new commands, the migrated behaviors of/issue-startand/issue-close, the/iflowstate machine, and the authoritative branch-derivedNrule).uv run issue-flow updateregenerates the in-tree.cursor/scaffold cleanly (19 files refreshed)./iflowon a fresh branch, on a branch with only_original.md, after/issue-plan, and after the status file flips to- [x] Done./issue-cleanupafter a real PR merges.Made with Cursor