issue-flow 0.6.0__tar.gz → 0.7.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {issue_flow-0.6.0 → issue_flow-0.7.0}/PKG-INFO +35 -61
- {issue_flow-0.6.0 → issue_flow-0.7.0}/README.md +34 -60
- {issue_flow-0.6.0 → issue_flow-0.7.0}/pyproject.toml +1 -1
- {issue_flow-0.6.0 → issue_flow-0.7.0}/pyproject.toml.orig +1 -1
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/agent.py +28 -14
- issue_flow-0.7.0/src/issue_flow/changelog.py +171 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/cli.py +136 -5
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/config.py +11 -4
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/editors.py +4 -1
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/epicplan.py +1 -1
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/history.py +223 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/init.py +27 -13
- issue_flow-0.7.0/src/issue_flow/migrate.py +181 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/modes.py +22 -16
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/modes.toml +9 -19
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/queueplan.py +1 -1
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/skill_ownership.py +13 -2
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/step_profiles.py +11 -5
- issue_flow-0.7.0/src/issue_flow/step_profiles.toml +17 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/surfaces.py +61 -5
- issue_flow-0.7.0/src/issue_flow/templates/commands/_wrapper.md.j2 +5 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/designs/essential-tests.md.j2 +1 -1
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/designs/test-registry.md.j2 +1 -1
- issue_flow-0.7.0/src/issue_flow/templates/docs/issue-workflow.md.j2 +49 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/docs/this-project.md.j2 +1 -1
- issue_flow-0.7.0/src/issue_flow/templates/rules/CLAUDE.md.j2 +2 -0
- issue_flow-0.7.0/src/issue_flow/templates/rules/_body.md.j2 +65 -0
- issue_flow-0.7.0/src/issue_flow/templates/rules/issueflow-rules.mdc.j2 +8 -0
- issue_flow-0.7.0/src/issue_flow/templates/skills/_default_sync_recover.md.j2 +1 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_essential_tests_review.md.j2 +1 -1
- issue_flow-0.7.0/src/issue_flow/templates/skills/_noob_next.md.j2 +27 -0
- issue_flow-0.7.0/src/issue_flow/templates/skills/_resolve_project_root.md.j2 +3 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_worktree_start.md.j2 +4 -4
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/iflow_build/SKILL.md.j2 +2 -2
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_cleanup/SKILL.md.j2 +84 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_archive/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_cleanup/archive.md.j2 +3 -16
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_cleanup/classify.md.j2 +13 -0
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_cleanup/github.md.j2 +15 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_pr_sync/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_cleanup/prs.md.j2 +7 -26
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_cleanup/workspace.md.j2 +9 -0
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_close/SKILL.md.j2 +91 -0
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_close/changelog.md.j2 +84 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/gh_ci/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_close/ci.md.j2 +1 -14
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_close/merge.md.j2 +21 -0
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_close/ops.md.j2 +37 -0
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_close/sync.md.j2 +8 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_version_bump/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_close/version.md.j2 +14 -11
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/iflow_iflow/SKILL.md.j2 +11 -13
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_issue/SKILL.md.j2 +38 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_epic/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_issue/epic.md.j2 +10 -25
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_fix/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_issue/fix.md.j2 +8 -25
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_issue/new.md.j2 +42 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_review/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_issue/review.md.j2 +6 -25
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_split/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_issue/split.md.j2 +6 -23
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/iflow_pause/SKILL.md.j2 +2 -2
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_pick/SKILL.md.j2 +97 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_capture/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_pick/capture.md.j2 +3 -17
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_comments/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_pick/comments.md.j2 +4 -13
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/iflow_plan/SKILL.md.j2 +4 -4
- issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_run/SKILL.md.j2 +39 -0
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_auto/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_run/auto.md.j2 +23 -32
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_cycle/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_run/cycle.md.j2 +10 -27
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_drive/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_run/drive.md.j2 +20 -41
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_yolo/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_run/yolo.md.j2 +5 -19
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/iflow_setup/SKILL.md.j2 +11 -7
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_init/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_setup/harness.md.j2 +11 -30
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/iflow_status/SKILL.md.j2 +18 -10
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_doctor/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_status/doctor.md.j2 +13 -26
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_workspace_git/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_status/git.md.j2 +3 -21
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_graphify/SKILL.md.j2 → issue_flow-0.7.0/src/issue_flow/templates/skills/iflow_status/graph.md.j2 +4 -16
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templating.py +166 -81
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/tracking.py +3 -3
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/user_global.py +3 -3
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/versionplan.py +1 -1
- issue_flow-0.6.0/src/issue_flow/step_profiles.toml +0 -35
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-archive.md.j2 +0 -63
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-auto.md.j2 +0 -38
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-build.md.j2 +0 -85
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-capture.md.j2 +0 -138
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-cleanup.md.j2 +0 -127
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-close.md.j2 +0 -135
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-cycle.md.j2 +0 -47
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-doctor.md.j2 +0 -73
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-drive.md.j2 +0 -53
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-epic.md.j2 +0 -48
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-fix.md.j2 +0 -94
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-graphify.md.j2 +0 -72
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-init.md.j2 +0 -41
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-issue.md.j2 +0 -64
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-ops.md.j2 +0 -28
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-pause.md.j2 +0 -61
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-pick.md.j2 +0 -132
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-plan.md.j2 +0 -113
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-pr-sync.md.j2 +0 -34
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-review.md.j2 +0 -80
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-setup.md.j2 +0 -97
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-split.md.j2 +0 -68
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-status.md.j2 +0 -88
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-workspace-git.md.j2 +0 -26
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow-yolo.md.j2 +0 -82
- issue_flow-0.6.0/src/issue_flow/templates/commands/iflow.md.j2 +0 -101
- issue_flow-0.6.0/src/issue_flow/templates/docs/issue-workflow.md.j2 +0 -715
- issue_flow-0.6.0/src/issue_flow/templates/rules/CLAUDE.md.j2 +0 -1
- issue_flow-0.6.0/src/issue_flow/templates/rules/_body.md.j2 +0 -372
- issue_flow-0.6.0/src/issue_flow/templates/rules/issueflow-rules.mdc.j2 +0 -9
- issue_flow-0.6.0/src/issue_flow/templates/skills/_default_sync_recover.md.j2 +0 -11
- issue_flow-0.6.0/src/issue_flow/templates/skills/_noob_next.md.j2 +0 -80
- issue_flow-0.6.0/src/issue_flow/templates/skills/_resolve_project_root.md.j2 +0 -20
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_cleanup/SKILL.md.j2 +0 -121
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_close/SKILL.md.j2 +0 -153
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_history_update/SKILL.md.j2 +0 -118
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_issue/SKILL.md.j2 +0 -67
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_ops/SKILL.md.j2 +0 -41
- issue_flow-0.6.0/src/issue_flow/templates/skills/iflow_pick/SKILL.md.j2 +0 -97
- {issue_flow-0.6.0 → issue_flow-0.7.0}/LICENSE +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/__init__.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/config_ops.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/console_io.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/convert.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/dependencies.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/epic_session.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/gitutils.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/graphify.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/project.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/publishintent.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/py.typed +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/readiness.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/self_update.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/sync.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/__init__.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/commands/__init__.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/designs/python-quality-tools.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/docs/__init__.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/rules/AGENTS.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/rules/__init__.py +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_essential_tests_close_sanity.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_gh_body_file.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_invocation_forms.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_model_directive.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_pstack_LICENSE.txt +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/_worktree_close_remove.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/caveman/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/grill_me/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_blast_radius/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_bro/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_principle_fix_root_causes/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_principle_prove_it_works/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_principle_subtract_before_you_add/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_principle_test_behavior_not_implementation/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_tdd/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_technical_writing/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/skills/pstack_unslop/SKILL.md.j2 +0 -0
- {issue_flow-0.6.0 → issue_flow-0.7.0}/src/issue_flow/templates/tools/README.md.j2 +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: issue-flow
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.7.0
|
|
4
4
|
Summary: Agents should behave. Let them follow the issue flow.
|
|
5
5
|
Keywords: cursor,ai,agents,issue-tracking,workflow
|
|
6
6
|
Author: jepegit
|
|
@@ -60,11 +60,10 @@ your-project/
|
|
|
60
60
|
this-project.md # Hand-editable project brief (created if missing)
|
|
61
61
|
05-epics/ # Staged epic plans (epic<N>_plan.md)
|
|
62
62
|
.cursor/
|
|
63
|
-
skills/ # Agent Skills
|
|
64
|
-
#
|
|
65
|
-
# /iflow-init = harness cold-start)
|
|
63
|
+
skills/ # Agent Skills: 11 commands; each folder holds
|
|
64
|
+
# SKILL.md plus mode files (yolo.md, epic.md, …)
|
|
66
65
|
rules/
|
|
67
|
-
issueflow-rules.mdc #
|
|
66
|
+
issueflow-rules.mdc # Cursor pointer to the AGENTS.md block
|
|
68
67
|
AGENTS.md # Workflow rules (managed block; shared by all editors)
|
|
69
68
|
docs/
|
|
70
69
|
issue-workflow.md # Human-readable overview of the workflow
|
|
@@ -72,38 +71,32 @@ your-project/
|
|
|
72
71
|
|
|
73
72
|
The exact `agent_dir` and the per-editor rules file depend on which editor(s) you scaffold for — see [Editor support](https://github.com/jepegit/issue-flow/blob/main/docs/editors.md). `AGENTS.md` (written as a non-destructive managed block), `.issueflows/04-designs-and-guides/this-project.md` (a hand-editable project brief created only when missing), and `docs/issue-workflow.md` are shared by every editor.
|
|
74
73
|
|
|
75
|
-
The
|
|
76
|
-
|
|
77
|
-
1. `/iflow-
|
|
78
|
-
2.
|
|
79
|
-
3. `/iflow-build` —
|
|
80
|
-
4. `/iflow-close` — runs tests, optionally bumps
|
|
81
|
-
5. `/iflow-cleanup` — after the PR merges, switches to the default branch,
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
- `/iflow-auto` — unattended large-change orchestrator over a confirmed epic (cycle a stage, record `auto_status.md`, adversarial `review` may reopen/create). Off-path; never auto-dispatched.
|
|
99
|
-
- `/iflow-review` — review open GitHub issues and apply workflow labels (v1: the configured `yolo` label) behind one consolidated confirm. Off-path; never auto-dispatched.
|
|
100
|
-
- `/iflow-doctor` — scaffold health check (missing skills/commands, stale config). Off-path; never auto-dispatched.
|
|
101
|
-
- `/iflow-archive` — **condense the solved archive (destructive, gated)**: summarises selected `issue<N>_*` groups under `03-solved-issues/` into a dated `YYYY-MM-DD_archived_issues.md` file. The summary records the pre-archive git ref so every original file stays recoverable (`git show <ref>:<path>`). Deletes the source files only after one consolidated confirm. Default: archive all but the **5 most recent** solved groups; pass `keep <K>`, an explicit list of issue numbers, or `all`. Requires a **clean working tree**. Off-path; never auto-dispatched.
|
|
74
|
+
The Agent Skills give agents a repeatable flow and appear in the slash menu. In chat you can also type **`iflow plan`**, **`iflow pick 42`**, etc. (space-separated, no `/`) when your keyboard makes slash awkward. The linear path is:
|
|
75
|
+
|
|
76
|
+
1. `/iflow-pick` (or `iflow pick 42`) — chooses an issue, creates its branch or worktree, and captures it into `.issueflows/01-current-issues/`.
|
|
77
|
+
2. `/iflow-plan` — drafts `issue<N>_plan.md` and stops for your confirmation.
|
|
78
|
+
3. `/iflow-build` — implements the confirmed plan.
|
|
79
|
+
4. `/iflow-close` — runs tests, optionally bumps the version, adds changelog trailers to the commit, updates status files, commits, pushes, and opens a PR.
|
|
80
|
+
5. `/iflow-cleanup` — after the PR merges, switches to the default branch, pulls, and deletes landed local branches behind explicit confirms.
|
|
81
|
+
|
|
82
|
+
`/iflow` runs whichever of these is next for the focus issue. The full surface is eleven commands; the merged ones take a **mode** as their first word, and each mode's instructions live in a separate file inside the skill folder, so an agent reads only what it needs:
|
|
83
|
+
|
|
84
|
+
| Command | Modes | What it does |
|
|
85
|
+
|---|---|---|
|
|
86
|
+
| `/iflow` | — | Dispatcher: run the next of capture / plan / build / close. |
|
|
87
|
+
| `/iflow-setup` | `harness`, `check` | Get a project ready (uv, git, GitHub, scaffold). |
|
|
88
|
+
| `/iflow-pick` | `<N>`, `capture`, `fix`, `label:<L>` | Choose an issue, branch, and capture it. |
|
|
89
|
+
| `/iflow-plan` | — | Write the plan and stop for approval. |
|
|
90
|
+
| `/iflow-build` | — | Implement the approved plan. |
|
|
91
|
+
| `/iflow-pause` | — | Park unfinished work with resume notes. |
|
|
92
|
+
| `/iflow-close` | `yolo`, `ops`, `draft`, `bump` | Tests, bump, changelog trailers, commit, push, PR. |
|
|
93
|
+
| `/iflow-cleanup` | `all`, `github`, `prs`, `archive` | After merge: default branch, pull, delete landed branches. |
|
|
94
|
+
| `/iflow-run` | `yolo`, `cycle`, `auto`, `drive` | Hands-off runs under one up-front confirm. |
|
|
95
|
+
| `/iflow-issue` | `fix`, `epic`, `split`, `review` | Create and shape GitHub issues. |
|
|
96
|
+
| `/iflow-status` | `doctor`, `git`, `graph` | Read-only overview of every issue. |
|
|
102
97
|
|
|
103
98
|
See the [docs](https://issue-flow.readthedocs.io/) for worked recipes (review → cycle, epic publish, cycle queues).
|
|
104
99
|
|
|
105
|
-
The **Agent Skills** under `.cursor/skills/` carry the workflows for on-demand use with `/iflow-setup`, `/iflow-pick`, `/iflow`, `/iflow-init`, `/iflow-capture`, `/iflow-plan`, `/iflow-build`, `/iflow-pause`, `/iflow-close`, `/iflow-cleanup`, `/iflow-yolo`, `/iflow-fix`, `/iflow-issue`, `/iflow-split`, `/iflow-status`, `/iflow-workspace-git`, `/iflow-epic`, `/iflow-cycle`, `/iflow-auto`, `/iflow-review`, `/iflow-doctor`, `/iflow-archive`, `@iflow-version-bump` when you need only the bump steps, or `@iflow-history-update` when you need only the changelog update (see [Cursor Agent Skills](https://cursor.com/help/customization/skills)).
|
|
106
|
-
|
|
107
100
|
## Prerequisites
|
|
108
101
|
|
|
109
102
|
issue-flow itself is a small Python CLI, but the **scaffolded commands and skills
|
|
@@ -116,7 +109,7 @@ Required:
|
|
|
116
109
|
- **[Git](https://git-scm.com/downloads)** — used by every slash command for
|
|
117
110
|
branch, fetch, status, commit, and push operations. Almost certainly already
|
|
118
111
|
installed if you're here, but the check covers it for completeness.
|
|
119
|
-
- **[GitHub CLI (`gh`)](https://cli.github.com/)** — used by `/iflow-
|
|
112
|
+
- **[GitHub CLI (`gh`)](https://cli.github.com/)** — used by `/iflow-pick` to
|
|
120
113
|
fetch issues, by `/iflow-close` to open PRs, and by `/iflow-cleanup` to check
|
|
121
114
|
PR merge status. After installing, run `gh auth login` once to authenticate.
|
|
122
115
|
|
|
@@ -154,7 +147,7 @@ Repos already scaffolded, toml missing: `issue-flow workspace init --default <ma
|
|
|
154
147
|
|
|
155
148
|
Recipe: [Use issue-flow in a folder of repos](docs/how-to/workspaces.md).
|
|
156
149
|
|
|
157
|
-
Lifecycle commands must still target the correct repo (`root:` / `repo:` hints, or `issue-flow agent resolve`). See `.issueflows/04-designs-and-guides/multi-repo-workspaces
|
|
150
|
+
Lifecycle commands must still target the correct repo (`root:` / `repo:` hints, or `issue-flow agent resolve`). See `.issueflows/04-designs-and-guides/workspaces.md#multi-repo-workspaces` in scaffolded projects.
|
|
158
151
|
|
|
159
152
|
### Optional: graphify integration
|
|
160
153
|
|
|
@@ -172,8 +165,7 @@ What `issue-flow` does when `graphify` is on PATH:
|
|
|
172
165
|
the graphify Cursor skill is registered alongside the issue-flow scaffold.
|
|
173
166
|
If graphify is not installed, both commands just print install hints and
|
|
174
167
|
continue — they never block.
|
|
175
|
-
-
|
|
176
|
-
for command-emitting editors) wraps
|
|
168
|
+
- The `/iflow-status graph` mode wraps
|
|
177
169
|
`issue-flow graphify`. With no extra args it runs `graphify update <project>`
|
|
178
170
|
— AST-only, **no LLM API key required**, so the no-arg case "just works".
|
|
179
171
|
For richer semantic relationships add `extract` (`issue-flow graphify extract`)
|
|
@@ -185,8 +177,8 @@ your shell environment. Cursor's own LLM is not available to subprocesses, so
|
|
|
185
177
|
graphify needs its own backend. Other subcommands (`watch`, `cluster-only`, …)
|
|
186
178
|
pass through too; trailing flags forward verbatim.
|
|
187
179
|
- The scaffolded rules and `/iflow-build` mention `graphify-out/GRAPH_REPORT.md`
|
|
188
|
-
as a recommended pre-read when the file exists.
|
|
189
|
-
|
|
180
|
+
as a recommended pre-read when the file exists. Nothing rebuilds the graph
|
|
181
|
+
automatically unless you set `auto_graphify_on_plan`.
|
|
190
182
|
|
|
191
183
|
To enable, install graphify as its own standalone tool:
|
|
192
184
|
|
|
@@ -201,7 +193,7 @@ pip install graphifyy
|
|
|
201
193
|
> **Why not an `issue-flow[graphify]` extra (or `uv tool install issue-flow --with graphifyy`)?**
|
|
202
194
|
> `uv tool install` only puts the **host package's** entry-point scripts on
|
|
203
195
|
> PATH. An extra (or `--with graphifyy`) pulls graphifyy into issue-flow's
|
|
204
|
-
> venv but leaves the `graphify` CLI invisible to the shell, so `/iflow-
|
|
196
|
+
> venv but leaves the `graphify` CLI invisible to the shell, so `/iflow-status graph`
|
|
205
197
|
> and `graphify cursor install` would still fail. Installing graphify as
|
|
206
198
|
> its own tool puts a real `graphify` shim on PATH and matches how we
|
|
207
199
|
> treat `git` / `gh`.
|
|
@@ -242,7 +234,7 @@ That's it. Open the project in your editor and, in the chat window:
|
|
|
242
234
|
| `iflow pick` | Shows you the open GitHub issues, you choose one, it creates a branch |
|
|
243
235
|
| `iflow plan` | Writes a plan and **stops** for you to approve it |
|
|
244
236
|
| `iflow build` | Implements the approved plan |
|
|
245
|
-
| `iflow close` | Runs tests,
|
|
237
|
+
| `iflow close` | Runs tests, writes changelog trailers into the commit, commits, pushes, opens a pull request |
|
|
246
238
|
| `iflow cleanup` | After the PR is merged: back to the main branch, tidy up local branches |
|
|
247
239
|
|
|
248
240
|
Forgot where you are? Type `iflow` and it runs the next step. (Slash forms
|
|
@@ -255,25 +247,7 @@ such as `/iflow-plan` work too.)
|
|
|
255
247
|
> and creating the GitHub repository. See
|
|
256
248
|
> [Getting started](https://issue-flow.readthedocs.io/en/latest/getting-started/).
|
|
257
249
|
|
|
258
|
-
|
|
259
|
-
|
|
260
|
-
- `/iflow-setup` — guided first-time setup for a new or unprepared project (`uv init`, `git init`, `gh auth login`, `gh repo create`), one confirmation at a time.
|
|
261
|
-
- `/iflow-init` — harness cold-start / check (`issue-flow init` / `update`). Does not capture issues.
|
|
262
|
-
- `/iflow-pick` — **front door**: helps pick the next issue (parked work first, else open GitHub issues ranked by milestone, labels, and similarity to recent work), creates the branch, and runs `/iflow-capture`.
|
|
263
|
-
- `/iflow` — **quick start**: inspects the current issue's state and dispatches to the right linear step automatically (a branch-derived number like `42-fix-login` is authoritative).
|
|
264
|
-
- `/iflow-pause` — park the current issue with a **Remaining work** note.
|
|
265
|
-
- `/iflow-yolo` — all-in-one chain (`capture → plan → build → close`) for small, low-risk issues, with up-front safeguards and a single consolidated confirm.
|
|
266
|
-
- `/iflow-fix` — interactive iterative-fixes session: one GitHub issue + long-lived branch, many small confirmed fixes.
|
|
267
|
-
- `/iflow-issue` — create one well-specified normal GitHub issue; optional branch + `/iflow-capture`.
|
|
268
|
-
- `/iflow-split` — cut an over-large issue into linked GitHub sub-issues.
|
|
269
|
-
- `/iflow-status` — **read-only** overview of where every issue stands, locally and on GitHub.
|
|
270
|
-
- `/iflow-workspace-git` — git snapshot (optional fetch) for every workspace member.
|
|
271
|
-
- `/iflow-epic` — staged epic plan + publish; decomposes into normal single-issue work.
|
|
272
|
-
- `/iflow-cycle` — batch yolo queue (`yolo` / `label:<L>` / numbers / epic).
|
|
273
|
-
- `/iflow-auto` — unattended epic stage via `/iflow-cycle` + adversarial `review`.
|
|
274
|
-
- `/iflow-review` — propose and apply workflow labels on open issues (v1: `yolo`).
|
|
275
|
-
- `/iflow-doctor` — scaffold health check.
|
|
276
|
-
- `/iflow-archive` — condense old solved-issue files into a dated summary (destructive, gated behind one consolidated confirm; originals stay recoverable via git).
|
|
250
|
+
Everything else lives in the merged commands: `iflow run yolo 42` for a small issue in one go, `iflow issue epic 42` to stage a big change, `iflow status doctor` to check the tracking folders, and so on. The table under [What it does](#what-it-does) lists every command and mode.
|
|
277
251
|
|
|
278
252
|
Docs cover epics, cycles, and reviews with examples:
|
|
279
253
|
https://issue-flow.readthedocs.io/
|
|
@@ -33,11 +33,10 @@ your-project/
|
|
|
33
33
|
this-project.md # Hand-editable project brief (created if missing)
|
|
34
34
|
05-epics/ # Staged epic plans (epic<N>_plan.md)
|
|
35
35
|
.cursor/
|
|
36
|
-
skills/ # Agent Skills
|
|
37
|
-
#
|
|
38
|
-
# /iflow-init = harness cold-start)
|
|
36
|
+
skills/ # Agent Skills: 11 commands; each folder holds
|
|
37
|
+
# SKILL.md plus mode files (yolo.md, epic.md, …)
|
|
39
38
|
rules/
|
|
40
|
-
issueflow-rules.mdc #
|
|
39
|
+
issueflow-rules.mdc # Cursor pointer to the AGENTS.md block
|
|
41
40
|
AGENTS.md # Workflow rules (managed block; shared by all editors)
|
|
42
41
|
docs/
|
|
43
42
|
issue-workflow.md # Human-readable overview of the workflow
|
|
@@ -45,38 +44,32 @@ your-project/
|
|
|
45
44
|
|
|
46
45
|
The exact `agent_dir` and the per-editor rules file depend on which editor(s) you scaffold for — see [Editor support](https://github.com/jepegit/issue-flow/blob/main/docs/editors.md). `AGENTS.md` (written as a non-destructive managed block), `.issueflows/04-designs-and-guides/this-project.md` (a hand-editable project brief created only when missing), and `docs/issue-workflow.md` are shared by every editor.
|
|
47
46
|
|
|
48
|
-
The
|
|
49
|
-
|
|
50
|
-
1. `/iflow-
|
|
51
|
-
2.
|
|
52
|
-
3. `/iflow-build` —
|
|
53
|
-
4. `/iflow-close` — runs tests, optionally bumps
|
|
54
|
-
5. `/iflow-cleanup` — after the PR merges, switches to the default branch,
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
- `/iflow-auto` — unattended large-change orchestrator over a confirmed epic (cycle a stage, record `auto_status.md`, adversarial `review` may reopen/create). Off-path; never auto-dispatched.
|
|
72
|
-
- `/iflow-review` — review open GitHub issues and apply workflow labels (v1: the configured `yolo` label) behind one consolidated confirm. Off-path; never auto-dispatched.
|
|
73
|
-
- `/iflow-doctor` — scaffold health check (missing skills/commands, stale config). Off-path; never auto-dispatched.
|
|
74
|
-
- `/iflow-archive` — **condense the solved archive (destructive, gated)**: summarises selected `issue<N>_*` groups under `03-solved-issues/` into a dated `YYYY-MM-DD_archived_issues.md` file. The summary records the pre-archive git ref so every original file stays recoverable (`git show <ref>:<path>`). Deletes the source files only after one consolidated confirm. Default: archive all but the **5 most recent** solved groups; pass `keep <K>`, an explicit list of issue numbers, or `all`. Requires a **clean working tree**. Off-path; never auto-dispatched.
|
|
47
|
+
The Agent Skills give agents a repeatable flow and appear in the slash menu. In chat you can also type **`iflow plan`**, **`iflow pick 42`**, etc. (space-separated, no `/`) when your keyboard makes slash awkward. The linear path is:
|
|
48
|
+
|
|
49
|
+
1. `/iflow-pick` (or `iflow pick 42`) — chooses an issue, creates its branch or worktree, and captures it into `.issueflows/01-current-issues/`.
|
|
50
|
+
2. `/iflow-plan` — drafts `issue<N>_plan.md` and stops for your confirmation.
|
|
51
|
+
3. `/iflow-build` — implements the confirmed plan.
|
|
52
|
+
4. `/iflow-close` — runs tests, optionally bumps the version, adds changelog trailers to the commit, updates status files, commits, pushes, and opens a PR.
|
|
53
|
+
5. `/iflow-cleanup` — after the PR merges, switches to the default branch, pulls, and deletes landed local branches behind explicit confirms.
|
|
54
|
+
|
|
55
|
+
`/iflow` runs whichever of these is next for the focus issue. The full surface is eleven commands; the merged ones take a **mode** as their first word, and each mode's instructions live in a separate file inside the skill folder, so an agent reads only what it needs:
|
|
56
|
+
|
|
57
|
+
| Command | Modes | What it does |
|
|
58
|
+
|---|---|---|
|
|
59
|
+
| `/iflow` | — | Dispatcher: run the next of capture / plan / build / close. |
|
|
60
|
+
| `/iflow-setup` | `harness`, `check` | Get a project ready (uv, git, GitHub, scaffold). |
|
|
61
|
+
| `/iflow-pick` | `<N>`, `capture`, `fix`, `label:<L>` | Choose an issue, branch, and capture it. |
|
|
62
|
+
| `/iflow-plan` | — | Write the plan and stop for approval. |
|
|
63
|
+
| `/iflow-build` | — | Implement the approved plan. |
|
|
64
|
+
| `/iflow-pause` | — | Park unfinished work with resume notes. |
|
|
65
|
+
| `/iflow-close` | `yolo`, `ops`, `draft`, `bump` | Tests, bump, changelog trailers, commit, push, PR. |
|
|
66
|
+
| `/iflow-cleanup` | `all`, `github`, `prs`, `archive` | After merge: default branch, pull, delete landed branches. |
|
|
67
|
+
| `/iflow-run` | `yolo`, `cycle`, `auto`, `drive` | Hands-off runs under one up-front confirm. |
|
|
68
|
+
| `/iflow-issue` | `fix`, `epic`, `split`, `review` | Create and shape GitHub issues. |
|
|
69
|
+
| `/iflow-status` | `doctor`, `git`, `graph` | Read-only overview of every issue. |
|
|
75
70
|
|
|
76
71
|
See the [docs](https://issue-flow.readthedocs.io/) for worked recipes (review → cycle, epic publish, cycle queues).
|
|
77
72
|
|
|
78
|
-
The **Agent Skills** under `.cursor/skills/` carry the workflows for on-demand use with `/iflow-setup`, `/iflow-pick`, `/iflow`, `/iflow-init`, `/iflow-capture`, `/iflow-plan`, `/iflow-build`, `/iflow-pause`, `/iflow-close`, `/iflow-cleanup`, `/iflow-yolo`, `/iflow-fix`, `/iflow-issue`, `/iflow-split`, `/iflow-status`, `/iflow-workspace-git`, `/iflow-epic`, `/iflow-cycle`, `/iflow-auto`, `/iflow-review`, `/iflow-doctor`, `/iflow-archive`, `@iflow-version-bump` when you need only the bump steps, or `@iflow-history-update` when you need only the changelog update (see [Cursor Agent Skills](https://cursor.com/help/customization/skills)).
|
|
79
|
-
|
|
80
73
|
## Prerequisites
|
|
81
74
|
|
|
82
75
|
issue-flow itself is a small Python CLI, but the **scaffolded commands and skills
|
|
@@ -89,7 +82,7 @@ Required:
|
|
|
89
82
|
- **[Git](https://git-scm.com/downloads)** — used by every slash command for
|
|
90
83
|
branch, fetch, status, commit, and push operations. Almost certainly already
|
|
91
84
|
installed if you're here, but the check covers it for completeness.
|
|
92
|
-
- **[GitHub CLI (`gh`)](https://cli.github.com/)** — used by `/iflow-
|
|
85
|
+
- **[GitHub CLI (`gh`)](https://cli.github.com/)** — used by `/iflow-pick` to
|
|
93
86
|
fetch issues, by `/iflow-close` to open PRs, and by `/iflow-cleanup` to check
|
|
94
87
|
PR merge status. After installing, run `gh auth login` once to authenticate.
|
|
95
88
|
|
|
@@ -127,7 +120,7 @@ Repos already scaffolded, toml missing: `issue-flow workspace init --default <ma
|
|
|
127
120
|
|
|
128
121
|
Recipe: [Use issue-flow in a folder of repos](docs/how-to/workspaces.md).
|
|
129
122
|
|
|
130
|
-
Lifecycle commands must still target the correct repo (`root:` / `repo:` hints, or `issue-flow agent resolve`). See `.issueflows/04-designs-and-guides/multi-repo-workspaces
|
|
123
|
+
Lifecycle commands must still target the correct repo (`root:` / `repo:` hints, or `issue-flow agent resolve`). See `.issueflows/04-designs-and-guides/workspaces.md#multi-repo-workspaces` in scaffolded projects.
|
|
131
124
|
|
|
132
125
|
### Optional: graphify integration
|
|
133
126
|
|
|
@@ -145,8 +138,7 @@ What `issue-flow` does when `graphify` is on PATH:
|
|
|
145
138
|
the graphify Cursor skill is registered alongside the issue-flow scaffold.
|
|
146
139
|
If graphify is not installed, both commands just print install hints and
|
|
147
140
|
continue — they never block.
|
|
148
|
-
-
|
|
149
|
-
for command-emitting editors) wraps
|
|
141
|
+
- The `/iflow-status graph` mode wraps
|
|
150
142
|
`issue-flow graphify`. With no extra args it runs `graphify update <project>`
|
|
151
143
|
— AST-only, **no LLM API key required**, so the no-arg case "just works".
|
|
152
144
|
For richer semantic relationships add `extract` (`issue-flow graphify extract`)
|
|
@@ -158,8 +150,8 @@ your shell environment. Cursor's own LLM is not available to subprocesses, so
|
|
|
158
150
|
graphify needs its own backend. Other subcommands (`watch`, `cluster-only`, …)
|
|
159
151
|
pass through too; trailing flags forward verbatim.
|
|
160
152
|
- The scaffolded rules and `/iflow-build` mention `graphify-out/GRAPH_REPORT.md`
|
|
161
|
-
as a recommended pre-read when the file exists.
|
|
162
|
-
|
|
153
|
+
as a recommended pre-read when the file exists. Nothing rebuilds the graph
|
|
154
|
+
automatically unless you set `auto_graphify_on_plan`.
|
|
163
155
|
|
|
164
156
|
To enable, install graphify as its own standalone tool:
|
|
165
157
|
|
|
@@ -174,7 +166,7 @@ pip install graphifyy
|
|
|
174
166
|
> **Why not an `issue-flow[graphify]` extra (or `uv tool install issue-flow --with graphifyy`)?**
|
|
175
167
|
> `uv tool install` only puts the **host package's** entry-point scripts on
|
|
176
168
|
> PATH. An extra (or `--with graphifyy`) pulls graphifyy into issue-flow's
|
|
177
|
-
> venv but leaves the `graphify` CLI invisible to the shell, so `/iflow-
|
|
169
|
+
> venv but leaves the `graphify` CLI invisible to the shell, so `/iflow-status graph`
|
|
178
170
|
> and `graphify cursor install` would still fail. Installing graphify as
|
|
179
171
|
> its own tool puts a real `graphify` shim on PATH and matches how we
|
|
180
172
|
> treat `git` / `gh`.
|
|
@@ -215,7 +207,7 @@ That's it. Open the project in your editor and, in the chat window:
|
|
|
215
207
|
| `iflow pick` | Shows you the open GitHub issues, you choose one, it creates a branch |
|
|
216
208
|
| `iflow plan` | Writes a plan and **stops** for you to approve it |
|
|
217
209
|
| `iflow build` | Implements the approved plan |
|
|
218
|
-
| `iflow close` | Runs tests,
|
|
210
|
+
| `iflow close` | Runs tests, writes changelog trailers into the commit, commits, pushes, opens a pull request |
|
|
219
211
|
| `iflow cleanup` | After the PR is merged: back to the main branch, tidy up local branches |
|
|
220
212
|
|
|
221
213
|
Forgot where you are? Type `iflow` and it runs the next step. (Slash forms
|
|
@@ -228,25 +220,7 @@ such as `/iflow-plan` work too.)
|
|
|
228
220
|
> and creating the GitHub repository. See
|
|
229
221
|
> [Getting started](https://issue-flow.readthedocs.io/en/latest/getting-started/).
|
|
230
222
|
|
|
231
|
-
|
|
232
|
-
|
|
233
|
-
- `/iflow-setup` — guided first-time setup for a new or unprepared project (`uv init`, `git init`, `gh auth login`, `gh repo create`), one confirmation at a time.
|
|
234
|
-
- `/iflow-init` — harness cold-start / check (`issue-flow init` / `update`). Does not capture issues.
|
|
235
|
-
- `/iflow-pick` — **front door**: helps pick the next issue (parked work first, else open GitHub issues ranked by milestone, labels, and similarity to recent work), creates the branch, and runs `/iflow-capture`.
|
|
236
|
-
- `/iflow` — **quick start**: inspects the current issue's state and dispatches to the right linear step automatically (a branch-derived number like `42-fix-login` is authoritative).
|
|
237
|
-
- `/iflow-pause` — park the current issue with a **Remaining work** note.
|
|
238
|
-
- `/iflow-yolo` — all-in-one chain (`capture → plan → build → close`) for small, low-risk issues, with up-front safeguards and a single consolidated confirm.
|
|
239
|
-
- `/iflow-fix` — interactive iterative-fixes session: one GitHub issue + long-lived branch, many small confirmed fixes.
|
|
240
|
-
- `/iflow-issue` — create one well-specified normal GitHub issue; optional branch + `/iflow-capture`.
|
|
241
|
-
- `/iflow-split` — cut an over-large issue into linked GitHub sub-issues.
|
|
242
|
-
- `/iflow-status` — **read-only** overview of where every issue stands, locally and on GitHub.
|
|
243
|
-
- `/iflow-workspace-git` — git snapshot (optional fetch) for every workspace member.
|
|
244
|
-
- `/iflow-epic` — staged epic plan + publish; decomposes into normal single-issue work.
|
|
245
|
-
- `/iflow-cycle` — batch yolo queue (`yolo` / `label:<L>` / numbers / epic).
|
|
246
|
-
- `/iflow-auto` — unattended epic stage via `/iflow-cycle` + adversarial `review`.
|
|
247
|
-
- `/iflow-review` — propose and apply workflow labels on open issues (v1: `yolo`).
|
|
248
|
-
- `/iflow-doctor` — scaffold health check.
|
|
249
|
-
- `/iflow-archive` — condense old solved-issue files into a dated summary (destructive, gated behind one consolidated confirm; originals stay recoverable via git).
|
|
223
|
+
Everything else lives in the merged commands: `iflow run yolo 42` for a small issue in one go, `iflow issue epic 42` to stage a big change, `iflow status doctor` to check the tracking folders, and so on. The table under [What it does](#what-it-does) lists every command and mode.
|
|
250
224
|
|
|
251
225
|
Docs cover epics, cycles, and reviews with examples:
|
|
252
226
|
https://issue-flow.readthedocs.io/
|
|
@@ -40,7 +40,7 @@ from issue_flow import (
|
|
|
40
40
|
)
|
|
41
41
|
from issue_flow.config import Settings
|
|
42
42
|
from issue_flow.editors import DEFAULT_EDITOR, EDITORS
|
|
43
|
-
from issue_flow.templating import packaged_skill_output_names
|
|
43
|
+
from issue_flow.templating import RETIRED_SKILLS, packaged_skill_output_names
|
|
44
44
|
|
|
45
45
|
|
|
46
46
|
def _folders(project_root: Path, settings: Settings) -> dict[str, Path]:
|
|
@@ -141,7 +141,7 @@ def run_state(project_root: Path, console: Console, as_json: bool) -> int:
|
|
|
141
141
|
}
|
|
142
142
|
elif focus.resolved_via != "ambiguous":
|
|
143
143
|
# No focus yet — surface active-epic next_candidates so /iflow can
|
|
144
|
-
# recommend /iflow-pick instead of a blind /iflow-
|
|
144
|
+
# recommend /iflow-pick instead of a blind /iflow-pick (issue #210).
|
|
145
145
|
epic_hint = _collect_epic_hints(project_root, local=False)
|
|
146
146
|
payload["epic_hint"] = epic_hint
|
|
147
147
|
if not epic_hint["epics"]:
|
|
@@ -2565,7 +2565,7 @@ def run_version_plan(
|
|
|
2565
2565
|
as_json: bool,
|
|
2566
2566
|
) -> int:
|
|
2567
2567
|
"""Plan the next version deterministically — the mechanical half of the
|
|
2568
|
-
release-strategy work in the iflow-
|
|
2568
|
+
release-strategy work in the version step of the iflow-close skill.
|
|
2569
2569
|
|
|
2570
2570
|
Read-only: detects the strategy from ``pyproject.toml``, reads the current
|
|
2571
2571
|
version (static field, or latest git tag), applies the PEP 440 bump
|
|
@@ -2966,7 +2966,7 @@ def run_epic_status(
|
|
|
2966
2966
|
) -> int:
|
|
2967
2967
|
"""Deterministic epic progress: stages, per-issue state, next candidates.
|
|
2968
2968
|
|
|
2969
|
-
Read-only. Parses ``epic<N>_plan.md`` (the contract the /iflow-epic skill
|
|
2969
|
+
Read-only. Parses ``epic<N>_plan.md`` (the contract the /iflow-issue epic skill
|
|
2970
2970
|
writes) and — unless ``local`` — resolves each published issue's state via
|
|
2971
2971
|
``gh``. A missing/unauthenticated ``gh`` degrades to ``state: "unknown"``
|
|
2972
2972
|
per issue rather than failing the command.
|
|
@@ -2980,7 +2980,7 @@ def run_epic_status(
|
|
|
2980
2980
|
)
|
|
2981
2981
|
payload = _build_epic_status_payload(project_root, number, local=local)
|
|
2982
2982
|
if payload is None:
|
|
2983
|
-
msg = f"no epic plan found at {plan_path}; draft one with /iflow-epic {number}."
|
|
2983
|
+
msg = f"no epic plan found at {plan_path}; draft one with /iflow-issue epic {number}."
|
|
2984
2984
|
if as_json:
|
|
2985
2985
|
_emit_json(console, {"epic": number, "error": msg})
|
|
2986
2986
|
else:
|
|
@@ -3427,7 +3427,7 @@ def run_queue(
|
|
|
3427
3427
|
],
|
|
3428
3428
|
"skipped_closed": [item.number for item in plan.skipped_closed],
|
|
3429
3429
|
"independent": plan.independent,
|
|
3430
|
-
# #386: the hands-off drivers (/iflow-cycle, /iflow-auto, /iflow-drive)
|
|
3430
|
+
# #386: the hands-off drivers (/iflow-run cycle, /iflow-run auto, /iflow-run drive)
|
|
3431
3431
|
# surface these in their confirm so the operator knows which issues
|
|
3432
3432
|
# will take the non-yolo lane (policy: cycle_nonyolo) instead of
|
|
3433
3433
|
# stopping the run.
|
|
@@ -5162,7 +5162,7 @@ def _audit_context(
|
|
|
5162
5162
|
|
|
5163
5163
|
# Every editor scaffold materializes this skill, so its presence under an agent
|
|
5164
5164
|
# directory is a reliable "issue-flow is scaffolded here" marker.
|
|
5165
|
-
_SCAFFOLD_MARKER_SKILL = Path("skills") / "iflow-
|
|
5165
|
+
_SCAFFOLD_MARKER_SKILL = Path("skills") / "iflow-setup" / "SKILL.md"
|
|
5166
5166
|
|
|
5167
5167
|
|
|
5168
5168
|
def audit_editor_scaffolds(
|
|
@@ -5194,7 +5194,7 @@ def audit_editor_scaffolds(
|
|
|
5194
5194
|
continue # skills scaffold already materialized
|
|
5195
5195
|
if (
|
|
5196
5196
|
profile.commands_dir
|
|
5197
|
-
and (agent_root / profile.commands_dir / "iflow-
|
|
5197
|
+
and (agent_root / profile.commands_dir / "iflow-setup.md").is_file()
|
|
5198
5198
|
):
|
|
5199
5199
|
continue # command scaffold present (skills-less layout)
|
|
5200
5200
|
findings.append(
|
|
@@ -5241,6 +5241,20 @@ def audit_unmanaged_editor_skills(
|
|
|
5241
5241
|
if entry.name in packaged:
|
|
5242
5242
|
continue
|
|
5243
5243
|
rel = entry.relative_to(project_root).as_posix()
|
|
5244
|
+
if entry.name in RETIRED_SKILLS:
|
|
5245
|
+
findings.append(
|
|
5246
|
+
tracking.DirtyFinding(
|
|
5247
|
+
code="retired_editor_skill",
|
|
5248
|
+
severity=tracking.SEVERITY_WARN,
|
|
5249
|
+
message=(
|
|
5250
|
+
f"Skill directory {rel!r} was retired by a newer "
|
|
5251
|
+
"issue-flow. `issue-flow update` removes it unless "
|
|
5252
|
+
"it was edited; then delete it by hand."
|
|
5253
|
+
),
|
|
5254
|
+
repairable=False,
|
|
5255
|
+
)
|
|
5256
|
+
)
|
|
5257
|
+
continue
|
|
5244
5258
|
findings.append(
|
|
5245
5259
|
tracking.DirtyFinding(
|
|
5246
5260
|
code="unmanaged_editor_skill",
|
|
@@ -5709,8 +5723,8 @@ def _print_config_guide(console: Console, cfg_path: Path) -> None:
|
|
|
5709
5723
|
console.print(
|
|
5710
5724
|
" [dim]- [bold]label_flows[/bold] / [bold]yolo_label[/bold] / "
|
|
5711
5725
|
"[bold]ops_label[/bold] / [bold]publish_label[/bold]: let issue labels "
|
|
5712
|
-
"pick the flow (e.g. a 'yolo' label runs /iflow-yolo; 'ops' runs "
|
|
5713
|
-
"/iflow-ops no-PR close; 'publish' bumps + releases after merge); "
|
|
5726
|
+
"pick the flow (e.g. a 'yolo' label runs /iflow-run yolo; 'ops' runs "
|
|
5727
|
+
"/iflow-close ops no-PR close; 'publish' bumps + releases after merge); "
|
|
5714
5728
|
"re-run 'issue-flow update' so the commands re-render.[/dim]"
|
|
5715
5729
|
)
|
|
5716
5730
|
console.print(
|
|
@@ -5750,9 +5764,9 @@ def _print_config_guide(console: Console, cfg_path: Path) -> None:
|
|
|
5750
5764
|
)
|
|
5751
5765
|
console.print(
|
|
5752
5766
|
" [dim]- [bold]pr_merge_method[/bold]: squash|merge|rebase for yolo "
|
|
5753
|
-
"close (default squash); [bold]cycle_max_issues[/bold]: /iflow-cycle "
|
|
5767
|
+
"close (default squash); [bold]cycle_max_issues[/bold]: /iflow-run cycle "
|
|
5754
5768
|
"queue cap (default 10); [bold]auto_adversarial_loops[/bold]: "
|
|
5755
|
-
"/iflow-auto inter-epoch budget (default 2; trailing loops:<n>).[/dim]"
|
|
5769
|
+
"/iflow-run auto inter-epoch budget (default 2; trailing loops:<n>).[/dim]"
|
|
5756
5770
|
)
|
|
5757
5771
|
console.print(
|
|
5758
5772
|
" [dim]- [bold]pstack_skills[/bold]: vendored pstack skills to scaffold "
|
|
@@ -6107,7 +6121,7 @@ def _status_payload(project_root: Path, local: bool) -> dict[str, Any]:
|
|
|
6107
6121
|
]
|
|
6108
6122
|
solved_numbers = sorted(tracking.group_issue_files(folders["solved"]))
|
|
6109
6123
|
|
|
6110
|
-
# An in-flight /iflow-cycle leaves a cycle_status.md in current-issues; a
|
|
6124
|
+
# An in-flight /iflow-run cycle leaves a cycle_status.md in current-issues; a
|
|
6111
6125
|
# finished one is archived to solved/, so its presence here means a batch
|
|
6112
6126
|
# run is paused or active.
|
|
6113
6127
|
cycle_active = (folders["current"] / "cycle_status.md").is_file()
|
|
@@ -6209,7 +6223,7 @@ def _render_status_text(
|
|
|
6209
6223
|
if payload.get("cycle_active"):
|
|
6210
6224
|
console.print(
|
|
6211
6225
|
"[bold]Cycle[/bold]: [yellow]in-flight[/yellow] "
|
|
6212
|
-
"(cycle_status.md present — resume with `/iflow-cycle resume`)"
|
|
6226
|
+
"(cycle_status.md present — resume with `/iflow-run cycle resume`)"
|
|
6213
6227
|
)
|
|
6214
6228
|
|
|
6215
6229
|
github = payload["github"]
|