From 20ca236361a8b1e7153550be56ee2692bd2a6719 Mon Sep 17 00:00:00 2001
From: mohitagw15856 <119053560+mohitagw15856@users.noreply.github.com>
Date: Thu, 29 Jan 2026 08:40:21 +0000
Subject: [PATCH] Create SKILL.md

---
 prd-template/SKILL.md | 94 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 94 insertions(+)
 create mode 100644 prd-template/SKILL.md

diff --git a/prd-template/SKILL.md b/prd-template/SKILL.md
new file mode 100644
index 0000000..2a2c557
--- /dev/null
+++ b/prd-template/SKILL.md
@@ -0,0 +1,94 @@
+---
+name: prd-template
+description: Product Requirements Document creation following proven PM template structure. Use when the user asks to create, write, draft, or help with a PRD, product requirements document, product spec, feature specification, or product documentation for a new feature or product.
+---
+
+# PRD Template Skill
+
+This skill helps create professional Product Requirements Documents following industry best practices.
+
+## Template Structure
+
+Every PRD should include these sections in order:
+
+### 1. Overview
+- **Problem Statement**: What problem are we solving? (2-3 sentences)
+- **Proposed Solution**: High-level description of what we're building (2-3 sentences)
+- **Success Metrics**: How we'll measure success (3-5 key metrics)
+
+### 2. Context & Background
+- **Why Now**: Why is this the right time?
+- **Strategic Alignment**: How does this align with company objectives?
+- **User Research Summary**: Key insights from research (if applicable)
+
+### 3. User Stories & Use Cases
+Format: "As a [user type], I want to [action] so that [benefit]"
+- Include 3-7 primary user stories
+- Add acceptance criteria for each
+
+### 4. Requirements
+**Functional Requirements:**
+- Must-have features (P0)
+- Should-have features (P1)
+- Nice-to-have features (P2)
+
+**Non-Functional Requirements:**
+- Performance expectations
+- Security considerations
+- Accessibility requirements
+
+### 5. Design & User Experience
+- Link to design mocks or wireframes
+- Key user flows
+- Edge cases and error states
+
+### 6. Technical Considerations
+- Architecture implications
+- Dependencies on other systems
+- Technical risks and mitigations
+
+### 7. Implementation Plan
+- **Phase 1 (MVP)**: What goes in first version
+- **Phase 2**: What comes next
+- **Phase 3**: Future enhancements
+
+### 8. Open Questions
+- Decisions that still need to be made
+- Stakeholders to consult
+- Research needed
+
+### 9. Appendix
+- Research links
+- Related documents
+- Competitive analysis
+
+## Writing Guidelines
+
+**Tone**: Clear, concise, actionable
+**Audience**: Engineers, designers, stakeholders
+**Length**: Aim for 3-6 pages for features, 8-12 for products
+
+**Best Practices:**
+- Use concrete examples over abstractions
+- Include "why" not just "what"
+- Make requirements testable
+- Link to supporting materials
+- Update as decisions are made
+
+## What Makes a Good PRD
+
+✅ **Do:**
+- Write from the user's perspective
+- Include specific success metrics
+- Address edge cases
+- Link to research and data
+- Make trade-offs explicit
+
+❌ **Don't:**
+- Write implementation details (that's tech spec)
+- Assume everyone has context
+- Leave requirements ambiguous
+- Skip the "why"
+- Forget about accessibility
+
+## Example PRD Opening