How do I install the To Issues skill?

Run npx skillmds@latest add sones3/to-issues in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is To Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with To Issues?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is To Issues free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published To Issues?

sones3 (@sones3) published this skill. Their other Agent Skills are listed on their SkillMD profile.

To Issues by sones3 — Agent Skill

Name: To Issues
Author: sones3

File contents

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.

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)

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

Do NOT close or modify the parent PRD issue.

---name: to-issuesdescription: 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.---# PRD to IssuesBreak a PRD into **independent GitHub issues**, where each issue is a fully deliverable work item.## Process### 1. Locate the PRDAsk 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 issuesBreak 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 startingFor 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 issuesFor 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 buildA 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 discussionSummarize the agreed decisions from the pre-coding discussion, including technologies, architecture, layout, components, and any points of attention.## User stories addressedReference by number from the parent PRD:- User story 3- User story 7</issue-template>Do NOT close or modify the parent PRD issue.

Frequently asked questions

To Issues