# Spec Execution

6-phase iterative specification execution workflow covering implementation, testing...

- Repository: https://github.com/a5c-ai/babysitter (1887 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add a5c-ai/babysitter --skill spec-execution -g -a claude-code -y`
Codex: `npx skills add a5c-ai/babysitter --skill spec-execution -g -a codex -y`
Cursor: `npx skills add a5c-ai/babysitter --skill spec-execution -g -a cursor -y`
Gemini CLI: `npx skills add a5c-ai/babysitter --skill spec-execution -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add a5c-ai/babysitter`

## Description

6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

- Read specification for requirements and architecture
- Implement each requirement following project conventions
- Add type definitions and JSDoc documentation
- Implement error handling for all failure modes

### Phase 2: Test Writing
- Write unit tests for each module/function
- Write integration tests for API boundaries
- Cover all acceptance criteria from the specification
- Test edge cases and error paths

### Phase 3: Code Review
- Verify all requirements are implemented
- Check acceptance criteria are tested
- Review architecture adherence
- Assess code quality

### Phase 4: Iterative Improvement
- Address review findings
- Fix failing tests
- Resolve architecture deviations
- Re-verify quality (convergence loop, max 3 cycles)

### Phase 5: Atomic Commit
- Group changes into logical atomic commits
- Descriptive messages following project conventions
- Separate production, test, and config changes
- Include specification reference

### Phase 6: Progress Tracking
- Requirement completion percentage
- Test coverage summary
- Quality score report
- Remaining work identification

## Quality Gate

Quality threshold defaults to 80. If not met after max improvement cycles, a human breakpoint is triggered for review.

## When to Use

- `/spec:execute [file]` slash command
- After spec creation when ready to implement

## Processes Used By

- `claudekit-spec-workflow` (execute mode)