# Task Breakdown Task

Convert complex concepts from Laboratory experiments or Gauntlet validations into actionable step-by-step task lists.

## Purpose

Transform validated concepts and creative ideas into concrete, executable tasks that can be managed through external task management systems or personal workflows.

## When to Use This Task

**Use this task when:**
- Laboratory session produced actionable concepts
- Gauntlet validation identified implementation-ready ideas
- Need step-by-step breakdown for concept execution
- Tasks will be managed in external task management system
- Quick task list needed without full epic/story process

## Process

### Step 1: Concept Analysis

**Source Context:**
- [ ] Concept source identified (Laboratory, Gauntlet, etc.)
- [ ] Core value proposition understood
- [ ] Success criteria defined
- [ ] Complexity level assessed

**Implementation Assessment:**
- [ ] Technical requirements outlined
- [ ] Resource needs identified
- [ ] Timeline expectations set
- [ ] Dependencies mapped

### Step 2: Task Decomposition

**Break down concept into actionable tasks using this hierarchy:**

#### Phase 1: Foundation Tasks
- Research and preparation activities
- Environment setup and tool preparation
- Dependency resolution
- Initial design or planning work

#### Phase 2: Core Implementation Tasks
- Primary feature development
- Core functionality implementation
- Key integration work
- Essential user-facing elements

#### Phase 3: Integration & Testing Tasks
- System integration work
- Quality assurance and testing
- Performance optimization
- Bug fixes and refinements

#### Phase 4: Deployment & Launch Tasks
- Deployment preparation
- Documentation creation
- User training or onboarding
- Launch activities and monitoring

### Step 3: Task Specification

For each identified task, create:

#### Task Format
```
Task: {{Specific, actionable task description}}
Category: {{Foundation/Core/Integration/Deployment}}
Estimated Time: {{hours or days}}
Dependencies: {{other tasks that must complete first}}
Acceptance Criteria: {{how to know task is complete}}
Resources Needed: {{tools, access, information required}}
```

#### Task Quality Standards
- Tasks are specific and actionable (not vague)
- Each task can be completed independently
- Time estimates are realistic (2-8 hours ideal)
- Dependencies are clearly identified
- Success criteria are measurable

### Step 4: Task List Generation

**Create structured task list:**

#### Project: {{Concept Name}}
**Goal:** {{What this concept will achieve}}
**Timeline:** {{Overall time estimate}}
**Priority:** {{High/Medium/Low}}

#### Foundation Phase ({{estimated days}})
1. {{Task 1 - Setup/Research}}
2. {{Task 2 - Environment preparation}}
3. {{Task 3 - Dependency resolution}}

#### Core Implementation ({{estimated days}})
4. {{Task 4 - Primary feature development}}
5. {{Task 5 - Core functionality}}
6. {{Task 6 - Key integration work}}

#### Integration & Testing ({{estimated days}})
7. {{Task 7 - System integration}}
8. {{Task 8 - Quality assurance}}
9. {{Task 9 - Performance optimization}}

#### Deployment & Launch ({{estimated days}})
10. {{Task 10 - Deployment preparation}}
11. {{Task 11 - Documentation}}
12. {{Task 12 - Launch activities}}

### Step 5: API Integration Preparation

**Prepare task data for external systems:**

#### Task Management System Format
- Task title and description
- Category/project assignment
- Priority level
- Estimated time
- Dependencies (task relationships)
- Acceptance criteria
- Due date (if applicable)

#### Supported Systems
- Custom task management API
- Asana API integration
- Trello board creation
- GitHub Issues
- Linear tasks
- Notion database

### Step 6: Validation & Review

**Task List Quality Check:**
- [ ] All tasks are specific and actionable
- [ ] Dependencies are correctly identified
- [ ] Time estimates are reasonable
- [ ] Tasks build logically toward goal
- [ ] Success criteria are clear

**Implementation Readiness:**
- [ ] No tasks are blocked by unresolved dependencies
- [ ] Resource requirements are available
- [ ] Timeline aligns with expectations
- [ ] Quality standards are maintainable

## Output
- Structured task list with phases and dependencies
- Task specifications ready for API integration
- Timeline and resource requirements summary
- Implementation readiness assessment