prd-construction

PRD Construction Skill

Use this skill when planning work that requires structured documentation before implementation.

When to Use This Skill

• New features
• Significant refactoring efforts
• Complex bug fixes requiring architectural changes
• Any work benefiting from upfront planning and user approval

DOs and DONTs

DO

• DO use the superpowers:brainstorming skill first to refine requirements before writing the PRD
• DO create a dedicated directory for each PRD with all related documents
• DO include measurable success metrics with current vs. target values
• DO group related changes into logical, cohesive PRs
• DO include acceptance criteria as checkboxes that can be marked complete
• DO list exact file paths to create/modify in the implementation plan
• DO specify dependencies between PRs when they exist
• DO update the PRD as work progresses (mark checkboxes, add notes)
• DO get user approval before starting implementation

DON'T

• DON'T include AI-specific instructions in PRD documents (e.g., "For Claude:", "AI should...")
• DON'T include meta-commentary about the document itself
• DON'T skip the brainstorming phase - requirements need refinement
• DON'T create one PR per commit - group related commits into cohesive PRs
• DON'T split logically related changes across multiple PRs unnecessarily
• DON'T start implementation before user approves the PRD
• DON'T leave acceptance criteria vague - make them verifiable
• DON'T forget to update status as work completes

---

PRD Template

# PRD: [Feature/Initiative Name]

## Document Information

| Field | Value |
|-------|-------|
| **PRD ID** | [SHORT-ID-001] |
| **Status** | Draft / In Review / Approved / In Progress / Completed |
| **Author** | [Author Name] |
| **Created** | YYYY-MM-DD |
| **Last Updated** | YYYY-MM-DD |

---

## 1. Overview

### 1.1 Problem Statement

[Describe the problem being solved. What pain points exist? Why does this matter?]

### 1.2 Goals

[Numbered list of specific, measurable goals]

1. [Goal 1]
2. [Goal 2]
3. [Goal 3]

### 1.3 Non-Goals

[What is explicitly out of scope for this initiative?]

- [Non-goal 1]
- [Non-goal 2]

### 1.4 Success Metrics

| Metric | Current | Target |
|--------|---------|--------|
| [Metric 1] | [value] | [value] |
| [Metric 2] | [value] | [value] |

---

## 2. Background

### 2.1 Current State

[Describe the current system/behavior that will be changed]

### 2.2 Technical Context

[Relevant technical details: architecture, dependencies, constraints]

---

## 3. Requirements

### 3.1 Functional Requirements

#### FR-1: [Requirement Name]
[Description of the requirement]

#### FR-2: [Requirement Name]
[Description of the requirement]

### 3.2 Non-Functional Requirements

#### NFR-1: [Requirement Name]
[Description: performance, security, maintainability, etc.]

---

## 4. Implementation Phases

[High-level overview of implementation phases]

### Phase 1: [Phase Name]
[Brief description, reference to implementation-plan.md for details]

### Phase 2: [Phase Name]
[Brief description]

---

## 5. Testing Strategy

### 5.1 Test Approach
[How will changes be tested? TDD requirements, test types]

### 5.2 Verification Checklist
- [ ] [Verification item 1]
- [ ] [Verification item 2]

---

## 6. Risks and Mitigations

| Risk | Impact | Likelihood | Mitigation |
|------|--------|------------|------------|
| [Risk 1] | High/Medium/Low | High/Medium/Low | [Mitigation strategy] |

---

## 7. Open Questions

[List any unresolved questions that need answers before or during implementation]

1. [Question 1]
2. [Question 2]

---

## 8. Related Documents

- [Implementation Plan](./implementation-plan.md)
- [Other supporting documents]