# Full Build Plan From PRD

**Command**: `full-build-plan-from-prd`  
**Purpose**: Generate comprehensive development task breakdown from Product Requirements Document  
**Category**: Architecture Planning & Project Management  
**Elicit**: true  
**Dependencies**: 
  - templates/project-task-list-tmpl.md

---

## Overview

Convert a comprehensive Product Requirements Document (PRD) and supporting architecture documentation into a detailed, logically ordered task list for systematic development. This task generates actionable development workflows that can be executed by development teams or AI coding assistants.

## Process

This task follows a **mandatory three-phase process** with user confirmation at each stage to ensure accuracy and alignment.

### Phase 1: Development Phase Planning

**Instructions:**
1. **Deep Analysis**: Read and fully understand the PRD's functional requirements, architecture, and constraints using advanced thinking
2. **Identify Major Phases**: Determine 3-7 development phases considering:
   - Dependencies between components (database → APIs → frontend)
   - Optimal build sequence (foundational-first vs feature-by-feature)
   - Technical complexity and resource requirements
   - Risk mitigation and validation checkpoints
3. **Present Phase Structure**: Output numbered list of development phases in dependency order
4. **Request Confirmation**: Ask user to approve phase structure before proceeding

**Required User Interaction**: 
> "This is the proposed development phase structure. Do you approve before I move on to outlining high-level tasks?"

### Phase 2: High-Level Task Generation

**Instructions:**
1. **Generate Parent Tasks**: For each approved phase, create 3-7 high-level parent tasks representing main milestones
2. **Ensure Logical Sequence**: Tasks must follow proper dependency order within each phase
3. **Present Task Structure**: Output tasks with clear numbering (1.0, 2.0, etc.)
4. **Request Authorization**: Ask for permission to proceed to detailed breakdown

**Required User Interaction**:
> "This is the high-level task plan for each phase. Are you ready to break these down into detailed sub-tasks? Respond with 'Go' to proceed."

### Phase 3: Detailed Task Breakdown & Output

**Instructions:**
1. **Create Actionable Sub-Tasks**: Break each parent task into specific, verifiable work items that:
   - Represent single, completable pieces of work
   - Include specific file paths and technical details
   - Can be executed without ambiguity
   - Follow proper technical dependencies
2. **Identify Relevant Files**: List all files that must be created or modified
3. **Generate Final Output**: Create comprehensive task list using project-task-list-tmpl.md template

## Elicitation Requirements

**Phase 1 Elicitation**:
```
📋 PHASE STRUCTURE APPROVAL REQUIRED

Based on PRD analysis, here is the proposed development phase structure:

1. **Phase 1: Foundation & Infrastructure**
   [Description of foundational setup]

2. **Phase 2: [Core System Component]**
   [Description of core functionality]

[... additional phases ...]

❓ APPROVAL REQUIRED: Do you approve this phase structure before I move on to outlining high-level tasks?

⏳ WAITING FOR: User approval to proceed to Phase 2
```

**Phase 2 Elicitation**:
```
📋 HIGH-LEVEL TASK APPROVAL REQUIRED

**Phase 1: Foundation & Infrastructure**
- [ ] 1.0 Initialize Project Repository & Environment
- [ ] 2.0 Configure Database Architecture  
- [ ] 3.0 Implement Authentication Foundation

[... additional phases and tasks ...]

❓ APPROVAL REQUIRED: Are you ready to break these down into detailed sub-tasks?

⏳ WAITING FOR: User to respond with 'Go' to proceed to Phase 3
```

## Output Format

Generate final task list using the following structure:

```markdown
# [Project Name] - Development Task List v1.0

**Project**: [Project Description]
**Generated**: [Date]
**Architecture Source**: [Source Documentation]
**Development Timeline**: [Estimated Timeline]
**Team Size**: [Recommended Team Size]

---

## Relevant Files

### **Core Project Structure**
- `package.json` - Project dependencies and scripts
- `next.config.js` - Framework configuration
[... additional core files with descriptions ...]

### **[Category] Structure**  
- `src/path/file.ts` - Description of file purpose
[... additional files by category ...]

### Notes
- Technical requirements and constraints
- Architecture decisions and rationale
- Quality gates and validation requirements

---

## Tasks

**Phase 1: [Phase Name]**

- [ ] 1.0 **Parent Task Name**
  - [ ] 1.1 Sub-task: Specific actionable work item
  - [ ] 1.2 Sub-task: Another specific work item
  - [ ] 1.3 Sub-task: Final work item for this parent task

- [ ] 2.0 **Next Parent Task**
  - [ ] 2.1 Sub-task: Detailed implementation step
  [... additional sub-tasks ...]

[... additional phases ...]

---

## Final Delivery Checklist

### **Technical Deliverables**
- [ ] Functional core system with requirements compliance
- [ ] Complete security implementation with audit completion
[... additional technical deliverables ...]

### **Quality Standards**
- [ ] Performance targets achieved (specific metrics)
- [ ] Security audit passed with zero critical vulnerabilities
[... additional quality standards ...]
```

## File Management

**Output Location**: Save to `/templates/[project-slug]/tasks-[project-slug]-v1.0.md`  
**Versioning**: Check for existing task lists and increment version number  
**Template Usage**: Use `templates/project-task-list-tmpl.md` for consistent formatting

## Success Criteria

1. **Complete Phase Coverage**: All development phases identified and ordered logically
2. **Actionable Tasks**: Every sub-task is specific, verifiable, and executable
3. **Technical Accuracy**: File paths, dependencies, and technical details are correct
4. **User Validation**: Both phase structure and high-level tasks approved by user
5. **Ready for Development**: Task list can be immediately used by development teams

## Dependencies

This task requires:
- Comprehensive PRD with functional requirements
- Technical architecture documentation 
- Database and API specifications
- Security and deployment requirements
- User approval at Phase 1 and Phase 2 checkpoints

---

**Usage**: Execute this task when you have complete PRD documentation and need systematic development planning  
**Output**: Comprehensive, actionable task list ready for development team execution  
**Validation**: User confirmation required at two critical checkpoints before final output