Description
The current Init → Start → Close workflow is a great foundation. However, to reduce friction during complex tasks, context switching, and post-merge cleanup, we should introduce a more granular set of commands.
Proposed New Commands
1. /issue-plan
Role: Formalize the "thinking" phase before any code is touched.
- Logic: Move the planning steps currently in
/issue-start into this dedicated command.
- Output: Generate an
issue<N>_plan.md file and require explicit user confirmation before moving to implementation.
2. /issue-pause
Role: Safely park work to switch context.
- Logic:
- Update the status file with "Remaining work".
- Immediately move the issue group to
.issueflows/02-partly-solved-issues/.
- Suggest a WIP commit or switch the user back to the default branch (
main/master).
3. /issue-cleanup
Role: Dedicated "janitor" for post-merge maintenance.
- Logic: * Extract the post-merge logic from
/issue-close (Step 7).
- Detect merged PRs via
gh pr view.
- Perform the "consolidated confirm" to delete local branches whose tips are reachable from the default branch.
4. /issue-yolo (or /issue-fast)
Role: An "all-in-one" command for minor bugfixes and documentation.
- Logic: Chained execution of
init -> start -> implement -> close in a single flow.
- Safeguards: * Must abort if tests (e.g.,
uv run pytest) fail.
- Refuse to run if the working tree is dirty with unrelated changes.
- Single confirmation at the start before performing automated commit/push/PR.
Implementation Tasks
Expected End-to-End Flow
/issue-init: Capture.
/issue-plan: Define approach.
/issue-start: Execute implementation.
/issue-pause: (Optional) Park work.
/issue-close: Land work.
/issue-cleanup: Final branch/folder hygiene.
Description
The current Init → Start → Close workflow is a great foundation. However, to reduce friction during complex tasks, context switching, and post-merge cleanup, we should introduce a more granular set of commands.
Proposed New Commands
1.
/issue-planRole: Formalize the "thinking" phase before any code is touched.
/issue-startinto this dedicated command.issue<N>_plan.mdfile and require explicit user confirmation before moving to implementation.2.
/issue-pauseRole: Safely park work to switch context.
.issueflows/02-partly-solved-issues/.main/master).3.
/issue-cleanupRole: Dedicated "janitor" for post-merge maintenance.
/issue-close(Step 7).gh pr view.4.
/issue-yolo(or/issue-fast)Role: An "all-in-one" command for minor bugfixes and documentation.
init->start->implement->closein a single flow.uv run pytest) fail.Implementation Tasks
/issue-plan.md.j2./issue-pause.md.j2./issue-cleanup.md.j2./issue-yolo.md.j2.cursor-issue-workflow.mdto reflect the expanded lifecycle.Expected End-to-End Flow
/issue-init: Capture./issue-plan: Define approach./issue-start: Execute implementation./issue-pause: (Optional) Park work./issue-close: Land work./issue-cleanup: Final branch/folder hygiene.