Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
appautomaton avatar

Issue Driven Workflow

  • 1 installs
  • 130 repo stars
  • Updated July 11, 2026
  • appautomaton/agent-designer

issue-driven-workflow is a Claude skill that turns a complex task into a plan and trackable Issue CSV, then executes the rows autonomously.

About

This skill breaks a complex task into a structured plan and a trackable Issue CSV, then executes the rows autonomously. A developer uses it when a task has multiple steps, needs research first, or benefits from status tracking before execution. It runs a plan -> issues -> implement -> test -> review loop, ordering CSV rows by dependency and updating each row's status as work completes.

  • Breaks complex tasks into a plan and trackable Issue CSV
  • Runs a plan -> issues -> implement -> test -> review loop
  • Executes CSV rows autonomously in dependency order with status tracking

Issue Driven Workflow by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #2,479 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 30, 2026 (Skillselion catalog sync)
At a glance

issue-driven-workflow capabilities & compatibility

Capabilities
planning · project management · orchestration
Use cases
planning · project management · orchestration
From the docs

What issue-driven-workflow says it does

Break down complex tasks into a structured plan and trackable Issue CSV, then execute autonomously.
SKILL.md
The CSV is your execution state. Read it to know where you are, update it as you work, keep driving forward.
SKILL.md
npx skills add https://github.com/appautomaton/agent-designer --skill issue-driven-workflow

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars130
Last updatedJuly 11, 2026
Repositoryappautomaton/agent-designer

What it does

Turn a multi-step task into a dependency-ordered Issue CSV and execute the rows autonomously with status tracking.

Who is it for?

Multi-step tasks that need research, status tracking, and a structured breakdown before execution.

Skip if: Trivial single-step tasks that do not need a plan or CSV tracking.

When should I use this skill?

A task has multiple steps or benefits from a structured, trackable breakdown before execution.

What you get

A validated Issue CSV drives autonomous, dependency-ordered execution with per-row status.

  • Plan markdown file
  • Trackable Issue CSV with per-row status

By the numbers

  • Three complexity tiers: simple, medium, complex
  • Three planning scripts: create_plan, list_plans, validate_issues_csv

Files

SKILL.mdMarkdownGitHub ↗

Issue-Driven Workflow

Philosophy

The plan and Issue CSV are a work amplifier. Front-load the thinking so the agent has a full plate of actionable work to execute autonomously — more rows means more useful work per run.

1. Planning (interactive) — search the web, read docs, ask questions, gather context. A thorough plan means more work the agent can do without stopping. 2. Execution (autonomous) — be proactive, not passive. Work through the CSV end-to-end. Maximize useful work per run — don't wait for permission on routine decisions.

The quality bar: every CSV row should be completable, testable, and markable DONE without further clarification.

E2E loop

plan → issues → implement → test → review

Planning (interactive)

1. Restate the task and assumptions. 2. Gather context — search the web, read project files, inspect dependencies. Make every plan section concrete, not aspirational. 3. Ask up to 2 clarification questions if unclear, then proceed with stated assumptions. 4. Draft the plan in chat using assets/_template.md. Choose complexity (simple|medium|complex). 5. Ask: "Reply CONFIRM to write the plan file." 6. On confirmation:

   python3 .codex/skills/issue-driven-workflow/scripts/create_plan.py \
     --task "<title>" --complexity <simple|medium|complex>

7. Do not edit code while planning.

Creating the CSV (interactive)

1. Generate after the plan is approved. 2. Break the plan into granular, independently actionable rows. 3. Fill all required columns — see references/issue-csv-spec.md. 4. Order by dependency chain. Set Dependencies so execution order is unambiguous. 5. Validate:

   python3 .codex/skills/issue-driven-workflow/scripts/validate_issues_csv.py <issues.csv>

Executing the CSV (autonomous)

The CSV is your execution state. Read it to know where you are, update it as you work, keep driving forward.

1. Read the CSV. Find the next TODO row in dependency order. 2. Set Dev_Status = DOING. Start working. 3. Complete the row — search, read, write, test, whatever it requires. 4. When Acceptance is met and Test_Method passes, set Dev_Status = DONE. 5. Self-review. Mark Review1_Status = DONE. 6. Immediately move to the next row. Read the CSV again, pick the next TODO, keep going. 7. After all rows are DONE, regression check. Mark Regression_Status = DONE per row. 8. Report progress briefly as you complete rows. 9. Only stop for genuinely blocking unknowns that affect correctness, safety, or irreversible actions.

If a row is too large, split it. If a row fails, fix it or flag it. If in a git repo, commit at natural boundaries. Edit the CSV directly — re-validate after edits.

Scripts

ScriptPurpose
create_plan.pyCreate a plan file with YAML frontmatter under plan/
list_plans.pyList existing plans (supports --query, --json)
validate_issues_csv.pyValidate Issue CSV schema and status values

Run with --help first. Scripts live in scripts/ relative to this skill.

Naming

Plans: plan/YYYY-MM-DD_HH-mm-ss-<slug>.md — Issue CSVs: issues/YYYY-MM-DD_HH-mm-ss-<slug>.csv — same timestamp/slug.

References

  • Issue CSV specread when creating or validating CSVs
  • Testing policyread when filling `Test_Method`
  • Plan template — structure with complexity tiers
  • CSV template — example rows with plan-to-CSV mapping

Related skills

FAQ

What is the execution loop?

plan -> issues -> implement -> test -> review, with the Issue CSV as the execution state.

When should you use it?

When a task has multiple steps, needs research before starting, or benefits from status tracking.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.