메뉴
Use when the user has an approved feature brief and wants a structured PRD written to .claude/prds/. Activates after feature-discovery completes or when the user says "write the PRD", "turn this into a PRD", "create a spec for".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user references or attaches Microsoft Office files (.doc, .docx, .xls, .xlsx, .ppt, .pptx), PDFs, images (.png, .jpg, .jpeg), or CSV/JSON/YAML from Teams or SharePoint and asks to extract, summarize, tabulate, or cross-reference their contents. Ships a runnable `extract.py` — invoke that directly rather than re-implementing extraction inline.
Use when the user asks to integrate a third-party REST or GraphQL API — fetching data, authenticating, handling rate limits, retrying on failure, and wiring responses into the application.
Use when the user reports a bug, shows a stack trace, says "something's broken", or asks for help debugging unexpected behavior. Covers reproduction, isolation, root cause, fix, and regression test — the full loop. Applies to any language or stack.
Use when the user asks to add, alter, or drop database tables or columns, create a migration script, or run schema changes safely against a live database.
Use when the user describes a rough feature idea and wants to clarify requirements, resolve open questions, and produce a clean brief before writing a PRD. Activates on phrases like "I want to build", "I have an idea for", "what if we added", "can we make a feature that".
Use when the user asks to produce a PowerPoint deck — presentations, status updates, data read-outs, or structured deliverables. Takes a JSON/YAML spec and writes a .pptx with consistent slide layouts (title, section, bullets, two-column, table). Ships a runnable `generate.py`.
| name | idea-to-prd |
| description | Use when the user has an approved feature brief and wants a structured PRD written to .claude/prds/. Activates after feature-discovery completes or when the user says "write the PRD", "turn this into a PRD", "create a spec for". |
You are a senior product manager writing a PRD that will be handed directly to engineers. It must be precise enough that an agent can decompose it into tasks without asking questions.
Save to: .claude/prds/[kebab-case-feature-name].md
# PRD: [feature-name]
## Overview
[1-2 sentences: what this is and why it matters]
## Problem Statement
[What is broken or missing today? Who is affected and how?]
## Goals
- [Measurable goal 1]
- [Measurable goal 2]
## Non-Goals
**Explicitly NOT building:**
- [exclusion 1]
- [exclusion 2]
## User Stories
- As a [user], I want to [action] so that [outcome]
- As a [user], I want to [action] so that [outcome]
## Functional Requirements
### [Requirement Group 1]
- REQ-01: [specific, testable requirement]
- REQ-02: [specific, testable requirement]
### [Requirement Group 2]
- REQ-03: [specific, testable requirement]
## Success Criteria
- [Metric]: [target] (e.g. "Report generation time < 25 seconds")
- [Metric]: [target]
## Key Metrics
- [KPI 1]: [target value]
- [KPI 2]: [target value]
## Constraints & Assumptions
**Technical Constraints:**
- [constraint 1]
- [constraint 2]
**Resource Constraints:**
- [timeline, team size, budget]
**Assumptions:**
- [assumption 1]
- [assumption 2]
## Out of Scope
**Explicitly NOT building:**
- [item 1]
- [item 2]
## Open Questions
- [ ] [question that needs resolution before or during implementation]