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 or feature into vertical-slice GitHub issues. An agent skill from macalbert/envilder.
Install To Issues
$ npx skills add macalbert/envilder --skill to-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install macalbert/envilder 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/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/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/macalbert/envilder/tree/main/.github/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/macalbert/envilder/tree/main/.github/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 macalbert/envilder --skill to-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install macalbert/envilder to-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/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/macalbert/envilder/tree/main/.github/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 macalbert/envilder --skill to-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install macalbert/envilder to-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/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/macalbert/envilder/tree/main/.github/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/macalbert/envilder.git --path .github/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 macalbert/envilder --skill to-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install macalbert/envilder to-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/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/macalbert/envilder/tree/main/.github/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 macalbert/envilder 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 macalbert/envilder --skill to-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/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/macalbert/envilder/tree/main/.github/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 macalbert/envilder --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 macalbert/envilder to-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/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/macalbert/envilder/tree/main/.github/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
- 138
- Token cost
- ~571 tokens
- SKILL.md length
- 201 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Break a plan or feature into vertical-slice GitHub issues. An agent skill from macalbert/envilder.
- Works in 5 steps: Understand the Plan → Slice Vertically → Order by Dependencies → …
- Decomposing work from ROADMAP.md
- SKILL.md covers Workflow and Rules
- Calls gh
What it does
To Issues is an agent skill from macalbert/envilder. Break a plan or feature into vertical-slice GitHub issues. Each issue is a tracer bullet: independently deliverable, testable, and mergeable. Use when decomposing work from ROADMAP.md, a PRD, or a conversation.
Its SKILL.md is about 570 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: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.
When your agent uses it
- Decomposing work from ROADMAP.md
- Tasks that involve PRD writing
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 b6a0327. 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 571 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 201 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 macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 201 words, ~571 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 or feature into vertical-slice GitHub issues. Each issue is a tracer bullet: independently deliverable, testable, and mergeable. Use when decomposing work from ROADMAP.md, a PRD, or a conversation.
Plan to Issues
Turn the current plan into a set of vertical-slice GitHub issues ready for implementation.
Workflow
1. Understand the Plan
If the plan is vague, interview the user briefly (max 3 questions) to clarify scope and boundaries. Check ROADMAP.md and existing issues for overlap.
2. Slice Vertically
Each issue must be a tracer bullet: a thin vertical slice that:
- Touches all necessary layers (domain → application → infrastructure → entry point)
- Is independently testable and mergeable
- Delivers observable value (even if small)
Anti-pattern: Horizontal slices like "add all domain entities", "add all tests", "wire DI for everything". These delay feedback.
3. Order by Dependencies
Number issues in implementation order. Earlier issues should unblock later ones. First issue should be the thinnest possible end-to-end path (the tracer bullet).
4. Format Each Issue
## Title
feat(scope): concise description
## Description
What this slice delivers and why it matters independently.
## Acceptance Criteria
- [ ] Criterion using Should/When language
- [ ] Tests pass: `{test command}`
- [ ] Lint passes: `{lint command}`
## Technical Notes
- Affected files/modules
- Key design decisions (reference ADRs if applicable)
- Dependencies on other issues (if any)5. Present for Approval
Show the full issue list as a numbered table before creating anything:
| # | Title | Scope | Depends On |
|---|-------|-------|------------|
| 1 | feat(sdk-dotnet): add ISecretProvider port | Domain | n/a |
| 2 | feat(sdk-dotnet): implement AWS SSM provider | Infra | #1 |Wait for user confirmation. Then create issues via gh issue create.
Rules
- Max 8 issues per plan: if more are needed, split into phases
- Each issue ≤ 1 day of work: if larger, slice thinner
- Use Conventional Commit format for titles
- Reference ADRs in technical notes when relevant
- Label issues with
needs-triageunless user specifies otherwise
© macalbert, 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 .github/skills/to-issues of macalbert/envilder.
Open the folder on GitHubat commit b6a0327
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 skillmacalbert/envilder | 138 | — | ~571 | 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 macalbert/envilder
All 30 skills in this repoCode Review Perspectives
macalbert/envilder
Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.
Common Architecture Decisions
macalbert/envilder
Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.
Common Git
macalbert/envilder
Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.
Common Testing Conventions
macalbert/envilder
Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).
Doc Maintenance
macalbert/envilder
Workflow for maintaining changelogs, READMEs, and documentation files.
Doc Sync
macalbert/envilder
Audit and synchronize documentation across website, READMEs, and docs/.
Related
Works with
Categories
Questions about To Issues
What does To Issues do?
Break a plan or feature into vertical-slice GitHub issues. An agent skill from macalbert/envilder. To Issues is an agent skill from macalbert/envilder. Break a plan or feature into vertical-slice GitHub issues.
When should I use To Issues?
To Issues fits situations like: decomposing work from ROADMAP.md; tasks that involve PRD writing.
How do I install To Issues in Claude Code?
Run `npx skills add macalbert/envilder --skill to-issues -a claude-code`. Or copy the skill folder (.github/skills/to-issues in macalbert/envilder) 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 macalbert/envilder --skill to-issues -a codex`. Or copy the skill folder (.github/skills/to-issues in macalbert/envilder) 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 macalbert/envilder --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 571 tokens (SKILL.md is roughly 2.3k 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?
macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.
Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.