implementation-execution
Execute development tasks to build features, producing code, tests, and configuration artifacts that satisfy specification requirements and comply with constitution standards.
Best use case
implementation-execution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Execute development tasks to build features, producing code, tests, and configuration artifacts that satisfy specification requirements and comply with constitution standards.
Teams using implementation-execution should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/implementation-execution/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How implementation-execution Compares
| Feature / Agent | implementation-execution | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Execute development tasks to build features, producing code, tests, and configuration artifacts that satisfy specification requirements and comply with constitution standards.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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 1. **Prepare environment** - Scaffold directories and configuration 2. **Execute independent tasks** - Parallel execution for tasks without dependencies 3. **Execute dependent tasks** - Sequential execution respecting dependency graph 4. **Run per-task tests** - Verify each task's acceptance criteria 5. **Validate against spec** - Check requirement coverage and story satisfaction 6. **Run integration tests** - Cross-component testing 7. **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`
Related Skills
generics-implementation
Expert skill for implementing parametric polymorphism including type parameter bounds, monomorphization, type erasure, variance, higher-kinded types, and associated types.
metadata-standards-implementation
Apply Dublin Core, METS, MODS, and other metadata schemas for digital collections and archival materials
iso-implementation-guide
ISO 9001:2015 Quality Management System implementation skill with gap assessment and documentation templates
SCD Implementation Generator
Generates Slowly Changing Dimension implementations across platforms
plan-implementation
Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.