菜单
Use when converting a PRD, product brief, or feature spec into GitHub-ready issues with labels, acceptance criteria, dependencies, and verification steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when reviewing AI-generated code, apps, workflows, skills, PRDs, GitHub repos, or automation outputs before accepting or publishing them. Trigger this whenever the user asks whether an agent's work is actually usable, complete, safe, non-hallucinated, or ready to merge.
Use when checking whether a web app, localhost build, demo URL, landing page, AI-generated frontend, or GitHub project actually works in the browser before shipping. Trigger this whenever the user asks to test, verify, inspect, QA, launch, debug UI, check console errors, check mobile responsiveness, or validate a project in a real browser.
Use when scanning GitHub Trending, GitHub Explore, or hot repositories to identify useful tools, product opportunities, skill/workflow ideas, and hype traps for builders.
Use when preparing a GitHub repository, skill pack, template, CLI, MCP server, or open source developer tool for public release. Trigger this whenever the user asks to publish, launch, tag a release, improve GitHub presentation, choose topics, write release notes, or make a repo more discoverable.
Use when converting a rough product, workflow, agent, skill, or developer tool idea into a lean PRD with scope, user stories, acceptance criteria, and launch plan.
Use when auditing a GitHub repository, open source project, skill pack, template, CLI, MCP server, or developer tool before publishing or promoting it.
| name | prd-to-issues |
| description | Use when converting a PRD, product brief, or feature spec into GitHub-ready issues with labels, acceptance criteria, dependencies, and verification steps. |
Use this skill to make a PRD executable. The output should be ready to paste into GitHub issues or hand to a coding agent.
## Release Slice
One paragraph describing what ships first.
## Issues
### 1. Title
Labels: `feature`, `mvp`
Size: S / M / L
Priority: P0 / P1 / P2
Goal:
Scope:
Acceptance Criteria:
Verification:
Dependencies:
Group issues into milestones when there is a natural release boundary:
After building, run launch-readiness to audit the repository for README quality, install experience, trust signals, and conversion gaps before publishing.