tasks

name	tasks
description	Break down an approved implementation plan into specific, actionable tasks.

Tasks Skill

Break down plans into actionable implementation tasks.

When to Activate

This skill is relevant when:

• Converting implementation plans to tasks
• Creating task breakdowns
• Organizing work into phases
• Preparing for implementation

Core Principles

Actionable

• Every task must be clear
• Implementable without ambiguity
• Concrete deliverables
• No vague descriptions

Granular

• Small enough to complete in one session
• 1-2 hours maximum
• Single responsibility per task
• Easy to verify completion

Sequential & TDD-Ordered

• Respect dependencies
• You can't fetch data before API exists
• Foundation before features
• Within each phase, test tasks come BEFORE implementation tasks
• Write the test (RED), then implement to pass (GREEN), then refactor

Comprehensive

• Don't miss the "small stuff"
• Include icons, types, tests
• Update documentation
• Complete feature coverage

Quick Checks

When creating task breakdowns, verify:

• All plan items converted to tasks
• Tasks are specific and actionable
• Granular enough (1-2 hours each)
• Dependencies respected
• Every implementation task has a preceding test task in same phase
• No separate "Verification & Tests" phase at the end — tests are interleaved
• Phases: Foundation → Logic (test→impl) → UI (test→impl) → Integration (test→impl) → Refactor
• Database tasks come first
• API tasks before UI tasks
• Parallelizable tasks marked with [P]
• Blocking tasks marked with [B]
• No missing "small stuff" (icons, types, tests)
• Completing all tasks equals completing feature
• Build and test tasks included