implementation-execution
npx machina-cli add skill a5c-ai/babysitter/implementation-execution --openclawImplementation 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
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/spec-kit/skills/implementation-execution/SKILL.mdView on GitHub Overview
Executes development tasks from the task list against a specification and constitution, producing code, tests, and configuration artifacts with progressive validation. Independent tasks run in parallel while dependent tasks execute sequentially according to the dependency graph.
How This Skill Works
1) Prepare environment by scaffolding directories and configuration. 2) Execute independent tasks in parallel. 3) Execute dependent tasks sequentially, respecting the dependency graph. 4) Run per-task tests to verify acceptance criteria. 5) Validate coverage against the spec and perform integration tests. 6) Final human review before quality checklist completion. 7) Use babysitter pipelines (spec-kit-implementation or orchestrator) to run the full workflow.
When to Use It
- 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
- During integration testing and before a human quality review
Quick Start
- Step 1: Prepare environment by scaffolding directories and configuration.
- Step 2: Execute independent tasks in parallel where possible.
- Step 3: Execute dependent tasks in order, run per-task tests, validate against spec, run integration tests, and perform human review.
Best Practices
- Ensure every line of code traces back to a specification requirement
- Maintain code quality to meet constitution standards
- Write tests that verify acceptance criteria for each task
- Scaffold environment and configuration before coding
- Parallelize independent tasks while honoring dependencies
Example Use Cases
- Scaffold a new API endpoint structure, implement code, add unit tests, and create config artifacts all aligned to the spec.
- Run independent feature tasks in parallel, then resolve dependent tasks in sequence to satisfy the dependency graph.
- Execute per-task tests as soon as code or config is produced to confirm acceptance criteria are met.
- Perform integration tests across components to ensure end-to-end correctness before release.
- Complete a human review and quality checklist to validate spec coverage and standards compliance.
