원클릭으로
to-prd
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 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.