issueflow

issueflow-skills

Issueflow is a Codex plugin and Agent Skills pack for issue-driven development with Git Flow-lite, plan governance, two-track planning, and compound learning.

It helps an agent follow a durable loop:

1. Discover or clarify the next issue through autonomous scan, plan-gap scan, or interactive brainstorming.
2. Shape medium-sized issues or a multi-issue wave.
3. Validate that the issue is implementation-ready.
4. Dispatch work from develop into isolated issue/<n>-<slug> branches or worktrees.
5. Implement inside issue scope only.
6. Prove the result with durable QA evidence.
7. Merge into develop only after merge-gate.
8. Capture reusable learning with issue-compound.
9. Promote from develop to main through release-gate.

Issueflow can start from a single detailed product plan. As the project grows, it keeps a compact plan anchor and optional docs/plan/ structure so agents can compare new work against product truth without loading every planning document.

Issueflow keeps long-running projects manageable by reading current pointers first and searching archives only when needed. Autonomous cycles preserve both macro direction, such as product promise and wave goal, and micro direction, such as the active issue, proof pointer, branch/worktree, and next action. Completed issue history should compact into docs/history/ or the repo's equivalent archive so PLAN_ANCHOR.md and CURRENT_STATE.md stay short. Autonomous cycles should combine related tiny findings into medium vertical slices, form waves when independent lanes exist, and keep the main agent focused on scheduling and integration.

Package Layout

This repository is also the plugin root.

issueflow-skills/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── .claude-plugin/marketplace.json
├── .agents/plugins/marketplace.json
├── skills/
├── references/
├── templates/
├── scripts/validate.py
└── OPERATING-MODEL.md

Codex loads the skills from ./skills/. The shared references and templates are packaged next to the skills so the whole workflow can be installed as one plugin.

Guides

• English guide
• Korean guide

Install For Codex

After publishing this repo to GitHub, add it as a Codex plugin marketplace:

codex plugin marketplace add <owner>/issueflow-skills --ref main
codex plugin marketplace upgrade issueflow-skills

Then restart Codex, open /plugins, choose the Issueflow Skills marketplace, and install Issueflow.

For local testing before publishing, run this from the repository root:

codex plugin marketplace add .

Direct skill installation with $skill-installer is possible, but the plugin install is preferred because it keeps all related skills, references, and templates together.

Install For Claude Code

Issueflow is also packaged as a Claude Code plugin marketplace. In Claude Code, add the marketplace and install the plugin:

/plugin marketplace add jugol/issueflow-skills
/plugin install issueflow@issueflow-skills

Claude plugin skills are namespaced. Invoke the umbrella skill directly with:

/issueflow:issueflow

For local testing before publishing, start Claude Code with the plugin directory:

claude --plugin-dir .

Update Across Computers

Use main as the marketplace ref when your computers should track the latest maintained version:

codex plugin marketplace add <owner>/issueflow-skills --ref main
codex plugin marketplace upgrade issueflow-skills

Run upgrade on each computer whenever you want to refresh the installed plugin cache. For unattended refresh, schedule that command with Task Scheduler, cron, or another local automation on each computer.

For Claude Code, refresh the marketplace and update the plugin:

claude plugin marketplace update issueflow-skills
claude plugin update issueflow@issueflow-skills

Use a release tag when a computer should stay pinned until you intentionally move it:

codex plugin marketplace add <owner>/issueflow-skills --ref v<version>

See UPDATE.md for publisher and consumer update workflows.

Skills