spec-execution
Spec-execution automates implementation of feature specifications through six sequential phases: coding the feature with documentation, writing comprehensive tests, conducting code review, iteratively improving until quality thresholds are met, creating atomic commits with descriptive messages, and generating progress reports. Use this skill after creating a specification file and when ready to systematically implement it with integrated quality validation.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/spec-execution && cp -r /tmp/spec-execution/library/methodologies/claudekit/skills/spec-execution ~/.claude/skills/spec-executionSKILL.md
- 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)
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
>-
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.