Module Authoring
dna-seq/just-dna-lite
Author, resolve, compile and publish a just-dna annotation module — the spec directory layout, the CSV column contracts and vocabularies, the enrich→compile pipeline, and the checks that decide…
Turn a large task into a persistent plan file and a trackable Issue CSV (local files, not an external issue tracker), then execute the issues autonomously with per-row status updates.
Install Issue Driven Workflow
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install appautomaton/agent-designer issue-driven-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/appautomaton/agent-designer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/issue-driven-workflow .claude/skills/issue-driven-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "issue-driven-workflow" agent skill from https://github.com/appautomaton/agent-designer/tree/main/skills/issue-driven-workflow into .claude/skills/issue-driven-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-driven-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/appautomaton/agent-designer/tree/main/skills/issue-driven-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install appautomaton/agent-designer issue-driven-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/agent-designer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/issue-driven-workflow .agents/skills/issue-driven-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-driven-workflow" agent skill from https://github.com/appautomaton/agent-designer/tree/main/skills/issue-driven-workflow into .agents/skills/issue-driven-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-driven-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install appautomaton/agent-designer issue-driven-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/agent-designer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/issue-driven-workflow .cursor/skills/issue-driven-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "issue-driven-workflow" agent skill from https://github.com/appautomaton/agent-designer/tree/main/skills/issue-driven-workflow into .cursor/skills/issue-driven-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-driven-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/appautomaton/agent-designer.git --path skills/issue-driven-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install appautomaton/agent-designer issue-driven-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/agent-designer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/issue-driven-workflow .gemini/skills/issue-driven-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "issue-driven-workflow" agent skill from https://github.com/appautomaton/agent-designer/tree/main/skills/issue-driven-workflow into .gemini/skills/issue-driven-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-driven-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install appautomaton/agent-designer issue-driven-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/appautomaton/agent-designer.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/issue-driven-workflow .github/skills/issue-driven-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "issue-driven-workflow" agent skill from https://github.com/appautomaton/agent-designer/tree/main/skills/issue-driven-workflow into .github/skills/issue-driven-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-driven-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install appautomaton/agent-designer issue-driven-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/agent-designer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/issue-driven-workflow .opencode/skills/issue-driven-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "issue-driven-workflow" agent skill from https://github.com/appautomaton/agent-designer/tree/main/skills/issue-driven-workflow into .opencode/skills/issue-driven-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-driven-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
issue-driven-workflow- GitHub stars
- 131
- Token cost
- ~1.6k tokens
- SKILL.md length
- 750 words
- Files
- 13 (incl. scripts, references, assets)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Turn a large task into a persistent plan file and a trackable Issue CSV (local files, not an external issue tracker), then execute the issues autonomously with per-row status updates.
- Works in 2 steps: Planning (interactive): search the web,… → Execution (autonomous): be proactive,…
- Work must survive across sessions
- SKILL.md covers Philosophy, E2E loop, Paths and Planning (interactive), plus 5 more sections
- Runs Python scripts from its folder; calls python3
What it does
Issue Driven Workflow is an agent skill from appautomaton/agent-designer. Turn a large task into a persistent plan file and a trackable Issue CSV (local files, not an external issue tracker), then execute the issues autonomously with per-row status updates. Use when work must survive across sessions or hand off between agents, when you need an auditable record of multi-step execution, or to resume a plans/ and issues/ pair from an earlier session. Do not use for single-session tasks that your harness's built-in plan or todo tracking already covers.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts, reference files and assets (for example `assets/_template.md`, `references/issue-csv-spec.md` and `references/testing-policy.md`).
It sits in Documents & Office, covering CSV and tabular files and Issue triage. The repository describes itself as: Portable SKILLs workspace for Claude Code, Codex, and Gemini — issue-driven workflows and cross-agent collaboration via bridge scripts with session continuity.
When your agent uses it
- Work must survive across sessions
- Hand off between agents
- You need an auditable record of multi-step execution
- Resume a plans/ and issues/ pair from an earlier session
Example prompts
- “/issue-driven-workflow”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Planning (interactive): search the web, read docs, ask questions, gather context. A thorough plan means more work the agent can do without…
- Execution (autonomous): be proactive, not passive. Work through the CSV end to end and do not wait for permission on routine decisions.
What it can do on your machine
Read from SKILL.md and the folder at commit b6e95dc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 8 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Issue Driven Workflow loads about 1.6k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 126 tokens; SKILL.md has 750 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: warnings
The automated check found patterns that need a careful read before installing.
- WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:15
ve. Work through the CSV end to end and do not wait for permission on routine decisions.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 750 words (~1,580 tokens).
“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.”
- name
- issue-driven-workflow
- metadata.short-description
- Plan file → Issue CSV → tracked autonomous execution
Files
SKILL.md and 12 other files (scripts, references, assets) in skills/issue-driven-workflow of appautomaton/agent-designer.
- SKILL.md
- assets/_template.csv
- assets/_template.md
- references/issue-csv-spec.md
- references/testing-policy.md
- scripts/create_issues.py
- scripts/create_plan.py
- scripts/issue_utils.py
- scripts/list_plans.py
- scripts/plan_utils.py
- scripts/read_plan_frontmatter.py
- scripts/update_issue.py
- scripts/validate_issues_csv.py
Open the folder on GitHubat commit b6e95dc
Compare with similar skills
Issue Driven Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Issue Driven Workflow this skillappautomaton/agent-designer | 131 | — | ~1.6k | Automated safety check: Warn | None | |
| Module Authoringdna-seq/just-dna-lite | 141 | — | ~4.8k | Automated safety check: Notes | AGPL-3.0 | |
| Odoo Security Rulessickn33/agentic-awesome-skills | 47k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Scenario Admin Analyticsscenario-labs/skills | 913 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Data Table Managern8n-io/n8n | 207k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Instrument Data To Allotropeaws-samples/amazon-bedrock-agents-healthcare-lifesciences | 274 | 2 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Odoo Security Rules
sickn33/agentic-awesome-skills
Expert in Odoo access control: ir.model.access.csv, record rules (ir.rule), groups, and multi-company security patterns.
Scenario Admin Analytics
scenario-labs/skills
A skill your agent uses when answering Scenario admin analytics questions about Creative Unit consumption, most-used models, usage by user or project, AI adoption observability, cached usage data…
- Official
Data Table Manager
n8n-io/n8n
Load before calling data-tables or parse-file. An agent skill from n8n-io/n8n.
- Official
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
Abuse Hunter
nexu-io/harness-engineering-guide
Detect and investigate bulk registration abuse on SaaS platforms.
More from appautomaton/agent-designer
Collaborating With Antigravity
appautomaton/agent-designer
Delegate tasks to Google's Antigravity CLI (agy) for prototyping, debugging, code review, and research.
Collaborating With Claude
appautomaton/agent-designer
Delegate tasks to Claude Code CLI for prototyping, debugging, and code review.
Collaborating With Codex
appautomaton/agent-designer
Delegate tasks to Codex CLI for prototyping, debugging, code review, implementation handoff, cross-model second opinions, and multi-turn Codex sessions via SESSIONID.
Collaborating With Grok
appautomaton/agent-designer
Delegate tasks to Grok CLI (xAI) for prototyping, debugging, code review, research, and cross-model second opinions.
Related
Categories
Questions about Issue Driven Workflow
What does Issue Driven Workflow do?
Turn a large task into a persistent plan file and a trackable Issue CSV (local files, not an external issue tracker), then execute the issues autonomously with per-row status updates. Issue Driven Workflow is an agent skill from appautomaton/agent-designer. Turn a large task into a persistent plan file and a trackable Issue CSV (local files, not an external issue tracker), then execute the issues autonomously with per-row status updates.
When should I use Issue Driven Workflow?
Issue Driven Workflow fits situations like: work must survive across sessions; hand off between agents; you need an auditable record of multi-step execution; resume a plans/ and issues/ pair from an earlier session.
How do I install Issue Driven Workflow in Claude Code?
Run `npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a claude-code`. Or copy the skill folder (skills/issue-driven-workflow in appautomaton/agent-designer) into .claude/skills/issue-driven-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Issue Driven Workflow in Codex?
Run `npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a codex`. Or copy the skill folder (skills/issue-driven-workflow in appautomaton/agent-designer) into .agents/skills/issue-driven-workflow in your project. Codex loads it when a task matches its description.
Can I use Issue Driven Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appautomaton/agent-designer --skill issue-driven-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-driven-workflow, .gemini/skills/issue-driven-workflow, .github/skills/issue-driven-workflow and .opencode/skills/issue-driven-workflow in your project.
What does Issue Driven Workflow need to run?
Going by SKILL.md and its folder, Issue Driven Workflow needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Issue Driven Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Issue Driven Workflow safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Issue Driven Workflow use?
No licence was found for Issue Driven Workflow or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Issue Driven Workflow use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Issue Driven Workflow?
Skills that share tags, products or a category with Issue Driven Workflow: Module Authoring (dna-seq/just-dna-lite, 141 stars), Odoo Security Rules (sickn33/agentic-awesome-skills, 47k stars), Scenario Admin Analytics (scenario-labs/skills, 913 stars) and Data Table Manager (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Driven Workflow?
appautomaton (a GitHub organization) maintains it in appautomaton/agent-designer, which has 131 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 13, 2026.
Source: appautomaton/agent-designer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.