spec-execution
Scannednpx machina-cli add skill a5c-ai/babysitter/spec-execution --openclawSpec Execution
Overview
Executes a feature specification through 6 iterative phases with quality-gated convergence. Each phase builds on the previous, with improvement cycles triggered when quality falls below threshold.
Six Phases
Phase 1: Implementation
- 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)
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/claudekit/skills/spec-execution/SKILL.mdView on GitHub Overview
Executes a feature specification through six iterative phases (implementation, testing, review, improvement, commit, and progress tracking). Each phase builds on the last, with a quality-gated convergence that triggers improvement cycles when quality thresholds are not met.
How This Skill Works
The workflow reads the specification, implements requirements with project conventions, and adds types and JSDoc. It then writes tests, undergoes code review, and iterates improvements until the quality gate is satisfied. Atomic commits with spec references are created and progress is tracked.
When to Use It
- /spec:execute [file] slash command
- When starting a new feature from a completed spec
- When you need unit and integration tests to validate acceptance criteria
- When you require quality gated convergence with up to 3 improvement cycles
- When you want explicit progress tracking for completion percentage, test coverage, and quality score
Quick Start
- Step 1: Read the spec and outline requirements and acceptance criteria
- Step 2: Execute Phase 1 through Phase 3, then run tests; begin iterative improvements if needed
- Step 3: Create atomic commits referencing the spec, then enable progress tracking and monitor the quality gate
Best Practices
- Start from a complete spec with acceptance criteria and architecture notes
- Implement with project conventions, add type definitions and JSDoc
- Write unit tests for modules and integration tests for API boundaries
- Run code review to verify requirements, tests, and architecture adherence
- Keep commits atomic with descriptive messages and a spec reference
Example Use Cases
- Add a new REST API endpoint following the six-phase workflow
- Refactor a module with spec driven tests and 3 cycle improvements
- Introduce a feature flag with spec execution for safe rollout
- Fix a failing integration by repeating phases until tests pass
- Onboard a complex feature with progress tracking and quality score reporting
