implementation-execution
// Execute development tasks to build features, producing code, tests, and configuration artifacts that satisfy specification requirements and comply with constitution standards.
Implementation Execution
Overview
Execute development tasks from the task list against the specification and constitution. Produces code, tests, and configuration artifacts with progressive validation. Independent tasks execute in parallel; dependent tasks execute sequentially respecting the dependency graph.
When to Use
- After task list is approved and analysis confirms readiness
- When implementing feature code against a specification
- When running per-task tests during implementation
- When validating implementation against specification requirements
Key Principle
Every line of code must trace back to a specification requirement. Code quality must meet constitution standards. Tests must verify acceptance criteria from the task definition.
Process
- Prepare environment - Scaffold directories and configuration
- Execute independent tasks - Parallel execution for tasks without dependencies
- Execute dependent tasks - Sequential execution respecting dependency graph
- Run per-task tests - Verify each task's acceptance criteria
- Validate against spec - Check requirement coverage and story satisfaction
- Run integration tests - Cross-component testing
- Human review - Approve implementation before quality checklist
Tool Use
Invoke via babysitter process: methodologies/spec-kit/spec-kit-implementation
Full pipeline: methodologies/spec-kit/spec-kit-orchestrator