菜单
Use to turn resolved conversation, repo evidence, or a plan into a concise PRD, spec, or implementation brief.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.
Use for UI components, design systems, atomic design, tokens, themes, hardcoded visuals, or missing design SSOT.
Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.
Use for visual PDFs: create, polish, export, verify decks, reports, proposals, one-pagers, or HTML-to-PDF.
Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing.
Use for real UI E2E smoke/regression proof across web, Flutter, browser, Chrome, or device flows, with artifacts.
基于 SOC 职业分类
| name | to-prd |
| description | Use to turn resolved conversation, repo evidence, or a plan into a concise PRD, spec, or implementation brief. |
Use this only after enough context is resolved to synthesize.
If major decisions are still open, route through grill-me first.
Load references/template.md before writing the PRD.
Coordinate with nearby skills:
codebase-design for module ownership and interface decisionstest-quality for behavior-facing testing decisionsto-issues after the PRD is accepted and should become work itemsDo not publish to GitHub, Linear, or any external tracker unless the user asks for that publish step explicitly.