project-execution

## When To Use - After planning phase completes - Ready to implement tasks - Need systematic execution with tracking - Want checkpoint-based validation - Executing task lists with dependencies - Monitoring progress and velocity ## When NOT To Use - No implementation plan exists (use `Skill(attune:project-planning)` first) - Still planning or designing (complete planning phase before execution) - Single isolated task (execute directly without framework overhead) - Exploratory coding or prototyping (use focused development instead) ## Integration **With superpowers**: - Uses `Skill(superpowers:executing-plans)` for systematic execution - Uses `Skill(superpowers:systematic-debugging)` for issue resolution - Uses `Skill(superpowers:verification-before-completion)` for validation - Uses `Skill(superpowers:test-driven-development)` for TDD workflow **Without superpowers**: - Standalone execution framework - Built-in checkpoint validation - Progress tracking patterns ## Execution Framework ### Pre-Execution Phase **Actions**: 1. Load implementation plan 2. Validate project initialized 3. Check dependencies installed 4. Review task dependency graph 5. Identify starting tasks (no dependencies) **Validation**: - ✅ Plan file exists and is valid - ✅ Project structure initialized - ✅ Git repository configured - ✅ Development environment ready ### Task Execution Loop **For each task in dependency order**: ```markdown 1. PRE-TASK - Verify dependencies complete - Review ac...