spec-creation
This Claude Code skill generates comprehensive feature specifications by analyzing codebase structure, patterns, and dependencies to produce requirements, acceptance criteria, architecture decisions, phased implementation plans, and risk analysis. Use it before starting new feature implementation or when planning complex changes that span multiple modules.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/spec-creation && cp -r /tmp/spec-creation/library/methodologies/claudekit/skills/spec-creation ~/.claude/skills/spec-creationSKILL.md
- Identify existing patterns and conventions
- Map dependencies and integration points
- Review existing tests for testing patterns
- Document technical constraints
## Specification Components
### Scope and Non-Goals
Clear boundaries on what the feature does and does not include.
### Functional Requirements
Detailed requirements with unique identifiers for tracking.
### Acceptance Criteria
Testable, measurable criteria for each requirement.
### Architecture Decisions
Decision records with rationale and alternatives considered.
### Implementation Plan
Phased approach ordered by dependency, not priority.
### Risk Analysis
Identified risks with probability, impact, and mitigation strategies.
### API Contracts and Data Models
Interface definitions and data model schemas.
### Test Strategy
Mapping of unit, integration, and E2E tests to requirements.
## Output
Specifications are saved to `docs/specs/{feature}.md` for reference by the execution workflow.
## When to Use
- `/spec:create [feature]` slash command
- Before starting a new feature implementation
- When planning complex multi-module changes
## Processes Used By
- `claudekit-spec-workflow` (create 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.