SkillsAdd

sones3/skills · Archived

prd-to-issues

Break a PRD into independent GitHub issues, with backend-first then frontend-linked workflow. Each issue is fully discussed before implementation. Use when converting a PRD to actionable work items.

First seen Mar 24, 2026

Installation

$ npx skills add sones3/skills --skill prd-to-issues
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

write-a-prd Same source
sones3/skills

Create a business-focused PRD through user interview, repo exploration, and rigorous clarificat…

21 installs
grill-me Same source
sones3/skills

Interview the user relentlessly about a plan or design until reaching shared understanding, res…

17 installs
ubiquitous-language Same source
sones3/skills

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambigu…

16 installs
start-next-issue Same source
sones3/skills

Suggests the next GitHub issue to work on from a PRD breakdown, confirms it with the user, and …

16 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from sones3/skills · top by installs.

npx skills add sones3/skills
write-a-prd 21 grill-me 17 ubiquitous-language 16 start-next-issue 16 start-implementation 13 discuss-in-french 12 to-prd 6 to-issues 5 improve-codebase-architecture 4 domain-model 4

Browse all from sones3/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,620 B
  • docs SUMMARY.md 219 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 36 installs

SKILL.md

PRD to Issues

Break a PRD into independent GitHub issues, where each issue is a fully deliverable work item.

Process

1. Locate the PRD

Ask the user for the PRD GitHub issue number or URL.

If the PRD is not already in your context window, fetch it with: gh issue view <number> --comments

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the system.

3. Draft issues

Break the PRD into independent backend and frontend issues:

  • Backend issues first: fully implementable, complete, no dependencies on frontend.
  • Frontend issues second: fully implementable once backend is ready, each linked to its related backend issue.

Each issue must be autonomous and deliverable on its own. Do not create partial or dependent slices.

4. Discuss implementation before starting

For each issue, before coding, discuss:

  • Technologies and tools to use (backend and frontend)
  • Architecture, endpoints, schema (backend)
  • Layout, components, interactions (frontend)
  • Any important design decisions or trade-offs
  • Questions or uncertainties

Iterate discussion until everyone is aligned and the issue can be started with clarity.

5. Create GitHub issues

For each approved issue, create a GitHub issue using: gh issue create

Create backend issues first, then frontend issues. In each frontend issue, reference its related backend issue.

<issue-template>

Parent PRD

#<prd-issue-number>

What to build

A concise description of this issue, describing the fully deliverable behavior. Reference specific sections of the parent PRD rather than duplicating content.

Acceptance criteria

  • Criterion 1
  • Criterion 2
  • Criterion 3

(Optional: tests recommended but not required)

Blocked by

  • None (issues are sequential: backend first, frontend second with reference to backend issue)

Related backend issue (for frontend only)

  • #<backend-issue-number>

Notes / Implementation discussion

Summarize the agreed decisions from the pre-coding discussion, including technologies, architecture, layout, components, and any points of attention.

User stories addressed

Reference by number from the parent PRD:

  • User story 3
  • User story 7

</issue-template>

Do NOT close or modify the parent PRD issue.