Agent skill

To Issues

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

GPL-3.0Auto-check passedProduct & Project Management

Install To Issues

skills CLI

$ npx skills add ywwynm/EverythingDone --skill to-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ywwynm/EverythingDone to-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/to-issues .claude/skills/to-issues && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "to-issues" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/to-issues into .claude/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", 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

$skill-installer install https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/to-issues

Type 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.

skills CLI

$ npx skills add ywwynm/EverythingDone --skill to-issues -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ywwynm/EverythingDone to-issues --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/to-issues .agents/skills/to-issues && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "to-issues" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/to-issues into .agents/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", 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.

skills CLI

$ npx skills add ywwynm/EverythingDone --skill to-issues -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ywwynm/EverythingDone to-issues --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/to-issues .cursor/skills/to-issues && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "to-issues" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/to-issues into .cursor/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", 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

$ gemini skills install https://github.com/ywwynm/EverythingDone.git --path .agents/skills/to-issues

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ywwynm/EverythingDone --skill to-issues -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ywwynm/EverythingDone to-issues --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/to-issues .gemini/skills/to-issues && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "to-issues" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/to-issues into .gemini/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", 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.

GitHub CLI

$ gh skill install ywwynm/EverythingDone to-issues

Installs 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).

skills CLI

$ npx skills add ywwynm/EverythingDone --skill to-issues -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/to-issues .github/skills/to-issues && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "to-issues" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/to-issues into .github/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", 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.

skills CLI

$ npx skills add ywwynm/EverythingDone --skill to-issues -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ywwynm/EverythingDone to-issues --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/to-issues .opencode/skills/to-issues && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "to-issues" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/to-issues into .opencode/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", 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: to-issues
GitHub stars: 144
Used in: 12 other repos
Token cost: ~893 tokens
SKILL.md length: 501 words
Files: 1
Skills in repo: 6
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Works in 5 steps: Gather context → Explore the codebase (optional) → Draft vertical slices → …
User wants to convert a plan into issues
SKILL.md covers Process, Parent, What to build and Acceptance criteria, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

To Issues is an agent skill from ywwynm/EverythingDone. Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Issue triage and PRD writing. It works with Android. The repository describes itself as: EverythingDone, an Android app to help you remember things, and finish them! The licence is GPL-3.0.

When your agent uses it

User wants to convert a plan into issues
Create implementation tickets
Break down work into issues

Example prompts

“/to-issues”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Gather context
Explore the codebase (optional)
Draft vertical slices
Quiz the user
Publish the issues to the issue tracker

What it can do on your machine

Read from SKILL.md and the folder at commit bc5f3f7. 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
No scripts in the folder and no shell commands in SKILL.md.
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

To Issues loads about 893 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 501 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~893

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 passed

The automated check found no risky patterns in SKILL.md.

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from ywwynm/EverythingDone at commit bc5f3f7, republished under its GPL-3.0 licence (© ywwynm). 501 words, ~893 tokens.

Download SKILL.mdSave it as .claude/skills/to-issues/SKILL.md (or your agent's skills folder).

name: to-issues
description: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

To Issues

Break a plan into independently-grabbable issues using vertical slices (tracer bullets).

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

3. Draft vertical slices

Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

<vertical-slice-rules>
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
- A completed slice is demoable or verifiable on its own
- Prefer many thin slices over few thick ones
</vertical-slice-rules>

4. Quiz the user

Present the proposed breakdown as a numbered list. For each slice, show:

Title: short descriptive name
Type: HITL / AFK
Blocked by: which other slices (if any) must complete first
User stories covered: which user stories this addresses (if the source material has them)

Ask the user:

Does the granularity feel right? (too coarse / too fine)
Are the dependency relationships correct?
Should any slices be merged or split further?
Are the correct slices marked as HITL and AFK?

Iterate until the user approves the breakdown.

Show full SKILL.md (197 more words)Show less

5. Publish the issues to the issue tracker

For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.

Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.

<issue-template>
## Parent

A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.

Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Acceptance criteria

Criterion 1
Criterion 2
Criterion 3

Blocked by

A reference to the blocking ticket (if any)

Or "None - can start immediately" if no blockers.

</issue-template>

Do NOT close or modify any parent issue.

Files

Just SKILL.md in .agents/skills/to-issues of ywwynm/EverythingDone.

Open the folder on GitHubat commit bc5f3f7

Used in 12 other repositories

We found 13 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 12 other GitHub owners. This page covers the copy in ywwynm/EverythingDone, which our catalogue first saw on October 7, 2026.

Compare with similar skills

To Issues 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.

To Issues compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
To Issues this skillywwynm/EverythingDone	144	12 repos	~893	Automated safety check: Pass	GPL-3.0	yesterday
To Issuesfossasia/eventyay-interpretation	1.6k	4 repos	~829	Automated safety check: Pass	Apache-2.0	4 days ago
To Prdfossasia/eventyay-interpretation	1.6k	4 repos	~755	Automated safety check: Pass	Apache-2.0	4 days ago
Setup Matt Pocock Skillsyamcodes/arkenv	147	—	~1.8k	Automated safety check: Pass	MIT	today
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Design Decknicobailon/pi-design-deck	292	—	~4.3k	Automated safety check: Pass	None	2 mo ago

Similar skills

To Issues
fossasia/eventyay-interpretation
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
1.6k GitHub starsUsed in 4 repos~829 tokens
Product & Project ManagementAuto-check passed
To Prd
fossasia/eventyay-interpretation
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
1.6k GitHub starsUsed in 4 repos~755 tokens
Product & Project ManagementAuto-check passed
Setup Matt Pocock Skills
yamcodes/arkenv
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
147 GitHub stars~1.8k tokensUpdated today
Agent WorkflowsAuto-check passed
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Design Deck
nicobailon/pi-design-deck
Present visual options for architecture, UI, and code decisions with high-fidelity side-by-side previews.
292 GitHub stars~4.3k tokensUpdated 2 mo ago
Product & Project ManagementAuto-check passed
Review
fossasia/eventyay-interpretation
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match…
1.6k GitHub starsUsed in 35 repos~996 tokens
Product & Project ManagementAuto-check passed

More from ywwynm/EverythingDone

Diagnose
ywwynm/EverythingDone
Disciplined diagnosis loop for hard bugs and performance regressions.
144 GitHub starsUsed in 17 repos~1.8k tokens
Auto-check passed
Triage
ywwynm/EverythingDone
Triage issues through a state machine driven by triage roles.
144 GitHub starsUsed in 9 repos~1.2k tokens
Auto-check passed
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
144 GitHub starsUsed in 15 repos~1.3k tokens
Auto-check passed
To Prd
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
144 GitHub starsUsed in 11 repos~777 tokens
Auto-check passed
Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
144 GitHub starsUsed in 8 repos~1.7k tokens
Auto-check passed

Works with

Android

Questions about To Issues

What does To Issues do?

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. To Issues is an agent skill from ywwynm/EverythingDone. Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

When should I use To Issues?

To Issues fits situations like: user wants to convert a plan into issues; create implementation tickets; break down work into issues.

How do I install To Issues in Claude Code?

Run `npx skills add ywwynm/EverythingDone --skill to-issues -a claude-code`. Or copy the skill folder (.agents/skills/to-issues in ywwynm/EverythingDone) into .claude/skills/to-issues in your project. Claude Code loads it when a task matches its description.

How do I install To Issues in Codex?

Run `npx skills add ywwynm/EverythingDone --skill to-issues -a codex`. Or copy the skill folder (.agents/skills/to-issues in ywwynm/EverythingDone) into .agents/skills/to-issues in your project. Codex loads it when a task matches its description.

Can I use To Issues 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 ywwynm/EverythingDone --skill to-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/to-issues, .gemini/skills/to-issues, .github/skills/to-issues and .opencode/skills/to-issues in your project.

What does To Issues need to run?

SKILL.md names no scripts, command-line tools or credentials: To Issues is instructions for the agent only.

Does To Issues 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 To Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does To Issues use?

To Issues is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does To Issues use?

About 893 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to To Issues?

Skills that share tags, products or a category with To Issues: To Issues (fossasia/eventyay-interpretation, 1.6k stars), To Prd (fossasia/eventyay-interpretation, 1.6k stars), Setup Matt Pocock Skills (yamcodes/arkenv, 147 stars) and CCPM Project Management (automazeio/ccpm, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains To Issues?

ywwynm (a GitHub user) maintains it in ywwynm/EverythingDone, which has 144 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.

Source: ywwynm/EverythingDone on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install To Issues

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

To Issues

Process

1. Gather context

2. Explore the codebase (optional)

3. Draft vertical slices

4. Quiz the user

5. Publish the issues to the issue tracker

What to build

Acceptance criteria

Blocked by

Files

Used in 12 other repositories

Compare with similar skills

Similar skills

More from ywwynm/EverythingDone

Related

Questions about To Issues