← Back to list

prd-writer
by dundas
⭐ 0🍴 0📅 Jan 16, 2026
SKILL.md
name: prd-writer description: Create a clear, actionable PRD with clarifying questions and a junior-friendly structure.
PRD Writer
Goal
Create a detailed Product Requirements Document (PRD) in Markdown from an initial feature prompt, suitable for a junior developer.
Process
- Receive initial prompt from user.
- Ask clarifying questions before writing. Provide options in letter/number lists for easy replies.
- Generate the PRD using the structure below.
- Save as
[n]-prd-[feature-name].mdunder/tasks/wherenis zero‑padded (e.g.,0001-prd-user-authentication.md).
Clarifying questions (guide)
- Problem/Goal: What problem does this solve? What is the main goal?
- Target User: Who is the primary user?
- Core Functionality: Key actions the user must perform?
- User Stories: Provide a few stories (As a…, I want…, so that…)
- Acceptance Criteria: How do we know it’s done/successful?
- Scope/Boundaries: Any explicit non-goals?
- Data Requirements: What data to display/manipulate?
- Design/UI: Any mockups/guidelines? Desired look/feel?
- Edge Cases: Potential edge cases and error conditions?
PRD Structure
- Introduction/Overview
- Goals
- User Stories
- Functional Requirements (numbered)
- Non-Goals (Out of Scope)
- Design Considerations (Optional)
- Technical Considerations (Optional)
- Success Metrics
- Open Questions
Output
- Format: Markdown (.md)
- Location:
/tasks/ - Filename pattern:
[n]-prd-[feature-name].md
Interaction
- Always ask clarifying questions before writing.
- Incorporate the answers and refine the PRD accordingly.
Key Principles
- No Arbitrary Timeframes: Never include time estimates, schedules, or delivery dates (e.g., "this will take 2-3 weeks", "Phase 1 in Q1"). Focus on what needs to be done, not when. Let users decide scheduling.
- Actionable Requirements: Provide concrete implementation steps and dependencies instead of timelines.
- Complexity Over Duration: If needed, indicate relative complexity (trivial/small/medium/large) rather than time estimates.
References
- See
reference.md.
Score
Total Score
60/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon