spec-driven-development skill
Specification creation and management for the Pilot Shell methodology. Covers semantic search, clarifying questions, structured spec generation, and iterative refinement.
A100/100content scan
Is the spec-driven-development skill safe?
Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.
No findings.
Install the spec-driven-development skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/a5c-ai/babysitter.git /tmp/babysitter mkdir -p ~/.claude/skills cp -r /tmp/babysitter/library/methodologies/pilot-shell/skills/spec-driven-development ~/.claude/skills/spec-driven-development
available in every project
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
- Search for files and code related to the task description
- Identify existing patterns that the spec should follow
- Map the impact area of proposed changes
- Generate SEARCH-CONTEXT.md with findings
2. Clarifying Question Resolution
- Identify ambiguities in the task description
- Generate targeted clarifying questions
- Resolve assumptions with explicit choices
- Document decisions for traceability
3. Spec Generation
- Structure specs with: title, goals, tasks, acceptance criteria
- Decompose into atomic, testable tasks
- Define dependency graphs between tasks
- Include rollback plans and risk assessments
- Generate SPEC.md document
4. Iterative Refinement
- Accept plan-reviewer feedback
- Apply revision requests by severity
- Refine task decomposition
- Update acceptance criteria
Spec Structure
# Specification: [Title]
## Goals
- [ ] Goal 1 with measurable outcome
## Tasks
### Task 1: [Description]
- **Acceptance Criteria**: ...
- **Test Strategy**: RED->GREEN->REFACTOR
- **Complexity**: low/medium/high
- **Dependencies**: [task-ids]
## Assumptions
- Assumption 1 (validated: yes/no)
## Risks
- Risk 1: Mitigation strategyMore skills from a5c-ai/babysitter
- Aadversarial-reviewFresh adversarial code review with binary PASS/FAIL verdicts, evidence citations, and anchoring bias prevention via fresh reviewer spawning.
- Aagent-boosterWASM-based instant code transforms for simple tasks, achieving 352x speedup over LLM inference with zero cost.
- Aagent-coordinationCoordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
- Aagent-dispatch
- Aanti-driftHierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
- Aarchitecture-design
- Aarchitecture-patternsSystem and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
- Aassimilate-popular-workflowsThis 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/.
- Aaudit-trail
- AbabysitOrchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
- Ababysit-babysitter-issuesThis 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.
- Abehavior-contractBug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.