spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.
npx skills add a5c-ai/babysitter --skill spec-execution --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- 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 breakpo
- Phase 2: Test Writing
- Phase 3: Code Review
- Phase 4: Iterative Improvement
- Phase 5: Atomic Commit
- Phase 6: Progress Tracking
- Quality Gate
- When to Use
- Processes Used By
What does the spec-execution skill do?
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill spec-execution --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.