to-issues
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). Use after /prd (and optionally /prd-to-spec) to turn requirements into actionable tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片, generate issues from PRD, issues from spec.
npx skills add smallnest/goal-workflow --skill to-issues --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# to-issues — PRD/SPEC to Issues Decompose a PRD and/or technical SPEC into small, independent, implementable Issues, then create them in your chosen platform. Works standalone — you don't need to have run `/prd` first. --- ## The Job 1. **Locate input** — find a PRD or SPEC file (auto-detect or user-specified) 2. **Decompose into Issues** — break User Stories into implementable tickets 3. **Review with user** — present Issue list for approval and adjustment 4. **Choose platform** — GitHub / Local / Baidu iCafe 5. **Create Issues** — create all tickets and print summary --- ## Step 1: Locate Input Find the input document: ``` What should I base the Issues on? A. Auto-detect: scan tasks/ for recent PRDs and SPECs B. Specific PRD file (e.g., tasks/prd-priority-system.md) C. Specific SPEC file (e.g., tasks/spec-priority-system.md) D. Both PRD and SPEC (best: PRD for requirements, SPEC for technical contracts) E. Paste requirements directly ``` If auto-detecting, list available files and let the user choose. If both PRD and SPEC are available, use the SPEC's Section 10.2 (Issue Mapping) as the primary guide, supplemented by PRD's User Stories. If only PRD is available, generate Issues
- The Job
- Step 1: Locate Input
- Step 2: Decompose into Issues
- Step 3: Choose Creation Mode
- Step 4: Mode-Specific Creation
- Mode A: GitHub
- Mode B: Local
- Mode C: Baidu iCafe
- Step 5: Summary Report
- Edge Cases & Fallback
- Relationship to Other Skills
gh issue create --title "[Title]" --body "[Description + Acceptance Criteria]" --label "[type]" --label "priority: [priority]" icafe-cli card create --space [SPACE] --title "[Title]" --description "[Description + Acceptance Criteria]" --cardtype "[Task/Bug/Story]"
What does the to-issues skill do?
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). Use after /prd (and optionally /prd-to-spec) to turn requirements into actionable tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片, generate issues from PRD, issues from spec.
How do I install it?
Run `npx skills add smallnest/goal-workflow --skill to-issues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From smallnest/goal-workflow, a repository with 199 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.