メニュー
Generates a structured PRD from a feature description or brief. Use when asked to write, draft, or create a PRD.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hamzafarooq/claude-code-starter --skill prd-generatorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Research emerging trends in a market or technology space. Returns signal vs noise breakdown with evidence. Use when the user asks what's changing in a market, what trends to watch, or what's coming next.
Turn any document, proposal, report, or outline into a stunning single-file HTML presentation using 34 pre-built professional templates. Use when the user wants to convert a markdown file, proposal, or written content into a beautiful visual HTML document ready to share or convert to PDF.
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
SOC 職業分類に基づく
SKILL.md を表示中
| name | prd-generator |
| description | Generates a structured PRD from a feature description or brief. Use when asked to write, draft, or create a PRD. |
When triggered, ask the user for:
Then generate a full PRD using the structure below.
What pain are we solving and for whom? Why does this matter now?
3-5 measurable outcomes we want to achieve with this feature. Format: "Increase [metric] by [amount] within [timeframe]"
What this feature explicitly will NOT do. Be specific. This section prevents scope creep.
Who uses this feature and in what context? Include 2-3 concrete scenarios (short narrative, not bullets).
Written as: "As a [user type], I want to [action] so that [outcome]." Group into: Must-have / Should-have / Nice-to-have
Written in Given/When/Then format for each must-have story. Should be specific enough that a QA engineer can write a test.
Two columns:
What must be decided before engineering starts? Format as questions, not statements. Assign an owner if known.
How will we measure whether this feature succeeded? Include leading indicators (early signals) and lagging indicators (final outcomes).
[ASSUMPTION][NEEDS INPUT]docs/prd.md