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.
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.
Install To Issues
$ npx skills add ayoubben18/ab-method --skill to-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ayoubben18/ab-method to-issues --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/ayoubben18/ab-method.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/to-issues .claude/skills/to-issues && 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 "to-issues" agent skill from https://github.com/ayoubben18/ab-method/tree/main/.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 install https://github.com/ayoubben18/ab-method/tree/main/.agents/skills/to-issuesType 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 ayoubben18/ab-method --skill to-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ayoubben18/ab-method to-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayoubben18/ab-method.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/to-issues .agents/skills/to-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "to-issues" agent skill from https://github.com/ayoubben18/ab-method/tree/main/.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.
$ npx skills add ayoubben18/ab-method --skill to-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ayoubben18/ab-method to-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayoubben18/ab-method.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/to-issues .cursor/skills/to-issues && 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 "to-issues" agent skill from https://github.com/ayoubben18/ab-method/tree/main/.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 https://github.com/ayoubben18/ab-method.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.
$ npx skills add ayoubben18/ab-method --skill to-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ayoubben18/ab-method to-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayoubben18/ab-method.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/to-issues .gemini/skills/to-issues && 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 "to-issues" agent skill from https://github.com/ayoubben18/ab-method/tree/main/.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.
$ gh skill install ayoubben18/ab-method to-issuesInstalls 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 ayoubben18/ab-method --skill to-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ayoubben18/ab-method.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/to-issues .github/skills/to-issues && 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 "to-issues" agent skill from https://github.com/ayoubben18/ab-method/tree/main/.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.
$ npx skills add ayoubben18/ab-method --skill to-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ayoubben18/ab-method to-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ayoubben18/ab-method.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/to-issues .opencode/skills/to-issues && 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 "to-issues" agent skill from https://github.com/ayoubben18/ab-method/tree/main/.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
- 192
- Token cost
- ~685 tokens
- SKILL.md length
- 368 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Break a plan, spec, or PRD into independently-grabbable GitHub issues 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
- Calls gh
What it does
To Issues is an agent skill from ayoubben18/ab-method. Break a plan, spec, or PRD into independently-grabbable GitHub issues 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 690 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 PRD writing. It works with GitHub. The repository describes itself as: A workflow system for Claude Code and Codex. It grills a problem into a domain-grounded plan, then either drives it through test-driven missions you review one at a time, or… The licence is MIT.
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.
What it can do on your machine
Read from SKILL.md and the folder at commit 85946e3. 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
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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 685 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 368 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 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 ayoubben18/ab-method at commit 85946e3, republished under its MIT licence (© ayoubben18). 368 words, ~685 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 GitHub issues 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 GitHub issues using vertical slices (tracer bullets).
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes a GitHub issue number or URL as an argument, fetch it with gh issue view <number> (with comments).
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code.
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 (105 more words)Show less
5. Create the GitHub issues
For each approved slice, create a GitHub issue using gh issue create. Use the issue body template below.
Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.
<issue-template>
## Parent#<parent-issue-number> (if the source was a GitHub 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.
Acceptance criteria
- Criterion 1
- Criterion 2
- Criterion 3
Blocked by
- Blocked by #
<issue-number>(if any)
Or "None - can start immediately" if no blockers.
</issue-template>Do NOT close or modify any parent issue.
© ayoubben18, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/to-issues of ayoubben18/ab-method.
Open the folder on GitHubat commit 85946e3
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| To Issues this skillayoubben18/ab-method | 192 | — | ~685 | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ouroboros PM InterviewQ00/ouroboros | 6.2k | 1 repos | ~5.7k | Automated safety check: Pass | MIT | |
| To Issuessmallnest/pigo | 475 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Write A Prdbestofjs/bestofjs | 3.1k | 1 repos | ~722 | Automated safety check: Pass | MIT | |
| Write Update Tidb Docspingcap/docs | 616 | — | ~2.3k | Automated safety check: Pass | Custom licence |
Similar skills
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
To Issues
smallnest/pigo
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).
Write A Prd
bestofjs/bestofjs
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue.
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
More from ayoubben18/ab-method
All 26 skills in this repoCodebase Design
ayoubben18/ab-method
Shared vocabulary and principles for designing deep modules — small interfaces, clean seams, testable through the interface.
Grill With Docs
ayoubben18/ab-method
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
Change Map
ayoubben18/ab-method
Draw a task's blast radius twice. An agent skill from ayoubben18/ab-method.
Handoff
ayoubben18/ab-method
Compact the current conversation (or a side-topic that surfaced mid-grill) into a handoff document another agent can pick up.
Improve Codebase Architecture
ayoubben18/ab-method
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Reconcile Roadmap
ayoubben18/ab-method
Cross-plan coherence critic for a whole roadmap. An agent skill from ayoubben18/ab-method.
Related
Works with
Categories
Questions about To Issues
What does To Issues do?
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. To Issues is an agent skill from ayoubben18/ab-method. Break a plan, spec, or PRD into independently-grabbable GitHub issues 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 ayoubben18/ab-method --skill to-issues -a claude-code`. Or copy the skill folder (.agents/skills/to-issues in ayoubben18/ab-method) 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 ayoubben18/ab-method --skill to-issues -a codex`. Or copy the skill folder (.agents/skills/to-issues in ayoubben18/ab-method) 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 ayoubben18/ab-method --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?
Going by SKILL.md and its folder, To Issues needs the command-line tools its instructions call (gh).
Does To Issues access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. 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 MIT 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 685 tokens (SKILL.md is roughly 2.7k 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: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), To Issues (smallnest/pigo, 475 stars) and Write A Prd (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains To Issues?
ayoubben18 (a GitHub user) maintains it in ayoubben18/ab-method, which has 192 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 1, 2026.
Source: ayoubben18/ab-method on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.