// Convert technical designs into actionable, sequenced implementation tasks. Create clear coding tasks that enable incremental progress, respect dependencies, and provide a roadmap for systematic feature development.
| name | task-breakdown |
| description | Convert technical designs into actionable, sequenced implementation tasks. Create clear coding tasks that enable incremental progress, respect dependencies, and provide a roadmap for systematic feature development. |
| license | MIT |
| compatibility | Claude Code, Cursor, VS Code, Windsurf |
| metadata | {"category":"methodology","complexity":"intermediate","author":"Kiro Team","version":"1.0.0"} |
Transform designs into actionable implementation plans. This skill teaches how to create well-structured task lists that enable efficient, systematic development.
Use task breakdown when:
- [ ] 1. [Epic/Major Component]
- [ ] 1.1 [Specific implementation task]
- [Implementation details]
- [Files/components to create]
- _Requirements: [Requirement references]_
- [ ] 1.2 [Next specific task]
- [Details]
- _Requirements: [References]_
- [ ] 2. [Next Epic/Major Component]
- [ ] 2.1 [Specific task]
Each task should include:
Identify all implementation needs:
Map what needs to be built first:
Order tasks to:
For each task, specify:
- [ ] X.Y [Task Title]
- [What to implement]
- [Files to create/modify]
- [Key functionality]
- [Tests to write]
- _Requirements: [Req-1, Req-2]_
Build core infrastructure before features.
1. Project setup and core interfaces
2. Data models and validation
3. Data access layer
4. Business logic services
5. API endpoints
6. Integration and wiring
Best for: New projects, complex systems
Build complete features end-to-end.
1. User registration (complete flow)
2. User authentication (complete flow)
3. User profile management (complete flow)
4. Advanced features
Best for: MVP development, early validation
Tackle uncertain areas early.
1. Most complex/uncertain components
2. External integrations
3. Core business logic
4. User interface
5. Polish and optimization
Best for: High uncertainty, proof-of-concepts
Combine approaches pragmatically.
1. Minimal foundation (core interfaces)
2. High-risk/high-value feature slice
3. Expand foundation as needed
4. Additional feature slices
5. Integration and polish
- [ ] 1. Set up project foundation
- [ ] 1.1 Create project structure and interfaces
- Set up directory structure
- Define TypeScript interfaces for core types
- Configure testing framework
- _Requirements: 1.1_
- [ ] 2. Implement data layer
- [ ] 2.1 Create core data models
- Implement User model with validation
- Add database migrations
- Write unit tests for validation
- _Requirements: 2.1, 2.2_
- [ ] 3. Implement business logic
- [ ] 3.1 Create authentication service
- Implement registration logic
- Add password hashing
- Create session management
- Write unit tests
- _Requirements: 1.2, 4.1_
- [ ] 4. Implement API layer
- [ ] 4.1 Create user endpoints
- Implement POST /users endpoint
- Add request validation
- Write integration tests
- _Requirements: 1.2, 2.3_
- [ ] 5. Integration and testing
- [ ] 5.1 Wire up components
- Connect services to API layer
- Implement middleware
- Add end-to-end tests
- _Requirements: 5.1_
- [ ] 2.1 Create User model with validation
- Implement User class with email, password, name fields
- Add email validation (RFC 5322 format)
- Add password validation (8+ chars, mixed case, numbers)
- Write unit tests for valid/invalid scenarios
- _Requirements: 1.2, 2.1_
- [ ] 2.1 Build user stuff
- Make user things work
- _Requirements: 1.2_
Appropriate: 2-4 hours of focused work
Too Large:
- [ ] 1.1 Implement complete user management system
Too Small:
- [ ] 1.1 Add semicolon to line 42
Just Right:
- [ ] 1.1 Create User model with validation methods
Technical Dependencies:
- [ ] 1.1 Create database connection ← Foundation
- [ ] 2.1 Create User model ← Depends on 1.1
- [ ] 3.1 Create UserService ← Depends on 2.1
Logical Dependencies:
- [ ] 1.1 User registration ← Must exist first
- [ ] 2.1 User login ← Depends on 1.1
- [ ] 3.1 Password reset ← Depends on 2.1
Problem:
UserService needs AuthService
AuthService needs UserService
Solution - Interface Extraction:
- [ ] 1.1 Create IUserService and IAuthService interfaces
- [ ] 1.2 Implement UserService using IAuthService
- [ ] 1.3 Implement AuthService using IUserService
- [ ] 1.4 Wire up dependency injection
# Implementation Plan: User Authentication
- [ ] 1. Set up authentication foundation
- [ ] 1.1 Create project structure and interfaces
- Set up directory structure for auth, models, API
- Define TypeScript interfaces for User, Session, AuthRequest
- Configure Jest for testing
- _Requirements: 1.1_
- [ ] 1.2 Set up database and migrations
- Configure database connection
- Create user and session tables
- Set up test database
- _Requirements: 1.1, 2.1_
- [ ] 2. Implement core data models
- [ ] 2.1 Create User model with validation
- Implement User class with email, password, profile fields
- Add email format validation
- Add password strength validation (8+ chars)
- Write unit tests for all validation rules
- _Requirements: 1.2, 2.1_
- [ ] 2.2 Create Session model
- Implement Session class with token, expiration
- Add session validation logic
- Write unit tests for session management
- _Requirements: 1.2, 4.1_
- [ ] 3. Create authentication services
- [ ] 3.1 Implement registration service
- Create UserService with register method
- Add password hashing with bcrypt
- Implement duplicate email checking
- Write unit tests for registration
- _Requirements: 1.2_
- [ ] 3.2 Implement login service
- Add login method with password verification
- Implement JWT token generation
- Create refresh token rotation
- Write unit tests for login flow
- _Requirements: 1.2, 4.1_
- [ ] 4. Create API endpoints
- [ ] 4.1 Implement registration endpoint
- Create POST /auth/register endpoint
- Add request validation middleware
- Implement error responses
- Write integration tests
- _Requirements: 1.2, 2.3_
- [ ] 4.2 Implement login endpoint
- Create POST /auth/login endpoint
- Add authentication middleware
- Implement logout functionality
- Write integration tests
- _Requirements: 1.2, 4.1_
- [ ] 5. Integration and security
- [ ] 5.1 Add security middleware
- Implement rate limiting
- Add CORS configuration
- Create JWT validation middleware
- Write security tests
- _Requirements: 4.1, 2.3_
- [ ] 5.2 End-to-end testing
- Create complete auth flow tests
- Test error scenarios
- Validate security measures
- _Requirements: 1.2, 4.1_
Before finalizing tasks:
Completeness:
Clarity:
Sequencing:
Feasibility:
Before starting a task:
During implementation:
Before marking complete:
After completing task breakdown:
Create comprehensive steering documents for development projects. Generates project-specific standards, git workflows, and technology guidelines in .kiro/steering/ directory.
Effective communication strategies for AI-assisted development. Learn context-first prompting, phased interactions, iterative refinement, and validation techniques to get better results from Claude and other AI coding assistants.
Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.
Comprehensive testing and validation strategies for spec-driven development. Learn phase-specific validation techniques, quality gates, and testing approaches to ensure high-quality implementation.
Transform vague feature ideas into clear, testable requirements using EARS format. Capture user stories, define acceptance criteria, identify edge cases, and validate completeness before moving to design.
Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.