Project Requirements Skill

Generate structured, AI-agent-optimized project documents following the Spec-Driven Development (SDD) methodology.

The SDD Workflow

Phase 1: Requirements → Phase 2: Design → Phase 3: Tasks → Phase 4: Implementation

Review happens at phase gates, not during implementation.

Note: Requirements discovery questions are handled by the product-manager agent's adaptive discovery system. This skill provides output templates only — do NOT run a separate interview.

Document Templates

1. PRD (Product Requirements Document)

# [Project Name] — Product Requirements Document

## 1. Executive Summary
[2-3 sentences: what, who, why]

## 2. Objectives & Success Metrics
| Objective | Metric | Target |
|-----------|--------|--------|
| [Goal]    | [KPI]  | [Number] |

## 3. User Personas
### Persona 1: [Name], [Role]
- Demographics: [Age, tech proficiency]
- Goals: [What they want]
- Pain points: [Current frustrations]

## 4. Feature List (Prioritized)
| ID | Feature | Priority | Description |
|----|---------|----------|-------------|
| F-001 | [Name] | P0 | [Description] |

## 5. User Stories with Acceptance Criteria
### US-001: [Title]
**As a** [role], **I want** [action] **so that** [benefit].
**Acceptance Criteria:**
- [ ] [Testable condition 1]
- [ ] [Testable condition 2]
- [ ] [Edge case handling]
**Dependencies:** [US-xxx]
**Priority:** P0

## 6. Business Rules
| ID | Rule | Example |
|----|------|---------|
| BR-001 | [Rule] | [Example] |

## 7. Non-Functional Requirements
| Category | Requirement | Target |
|----------|-------------|--------|
| Performance | Page load | < 2s |
| Security | Auth method | [method] |
| Accessibility | WCAG | AA |

## 8. Scope Boundaries
### In Scope: [list]
### Out of Scope: [list]

## 9. Technical Constraints
- Stack: [tech]
- Hosting: [platform]
- Compliance: [regulations]

## 10. Data Model Overview
| Entity | Key Fields | Relationships |
|--------|-----------|---------------|
| [Entity] | [fields] | [relations] |

2. Feature List JSON (for autonomous coding)

{
  "project": "[Name]",
  "features": [
    {
      "id": "F-001",
      "name": "[Feature]",
      "module": "[module]",
      "priority": "P0",
      "status": "pending",
      "depends_on": [],
      "acceptance_criteria": ["[criterion]"],
      "test_file": "tests/[path]"
    }
  ]
}

3. Task Breakdown

## TASK-001: [Title]
**Description:** [Detailed instructions]
**Dependencies:** blockedBy: [] | blocks: [TASK-002]
**Verification:** Run: `[command]` — Expect: [output]
**Files:** Create: [paths] | Modify: [paths]
**Commit:** `feat([scope]): [description]`
**Status:** pending

Writing Tips

• Number everything (US-001, BR-001, F-001)
• One requirement per bullet
• Acceptance criteria as checkboxes
• Include edge cases per story
• Specific: "tag appears in red" not "tags look nice"
• Update PRD as decisions change — living document