spec-driven-development

Solid

Specification creation and management for the Pilot Shell methodology. Covers semantic search, clarifying questions, structured spec generation, and iterative refinement.

AI & Automation 1,160 stars 71 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
79
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# spec-driven-development You are **spec-driven-development** -- the specification creation and management skill for Pilot Shell processes. ## Overview This skill provides the methodology for creating complete, reviewable specifications through semantic codebase search, clarifying question resolution, and structured spec generation. ## Capabilities ### 1. Semantic Codebase Search - 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 ```markdown # 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 - Assum...

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

spec-driven-development

Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

2 Updated today
LLl0k0laD
AI & Automation Listed

spec-driven-development

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

2 Updated 2 days ago
nota-america
AI & Automation Listed

spec-driven

Activate spec-driven development mode with enforced pipeline (SPEC→PLAN→IMPL→VERIF→SYNTHESE), 3-way triage (FULL/LIGHT/SHIP), token budgets, and explicit gates. Use when starting a feature, refactoring, or complex task that benefits from structured spec-first workflow. TRIGGERS: 'spec-driven', '/spec-driven', 'mode spec', 'spec first', 'pipeline complet', 'workflow structure'. Do NOT trigger on simple questions, quick fixes, or when user explicitly wants fast/informal mode.

3 Updated today
valorisa
AI & Automation Listed

specdd

Spec-driven development orchestrator that turns vague, top-of-mind feature requests into production-grade specifications before any code is written. ALWAYS use this skill whenever the user describes a feature, change, capability, screen, flow, or new component in plain language — even if they don't explicitly ask for a spec. Triggers on phrases like "build me", "make me", "add a feature", "I want to", "help me create", "implement", "let's build", "I need a", "can you make", "create a screen/page/component", or any new-feature request that lacks complete requirements (missing user stories, acceptance criteria, edge cases, error/empty/loading states, accessibility, or non-functional requirements). Interviews the user to fill gaps, applies UX/UI common sense, produces a structured spec + plan + tasks, then implements against the spec. Use this BEFORE writing any code for non-trivial features. Skip only for true one-liners (rename a variable, fix a typo, answer a research question) or work that is purely investig

1 Updated today
mnyok9939
Data & Documents Listed

spec-driven-develop

Automates pre-development workflow for large-scale complex tasks. Use when the user mentions "rewrite", "migrate", "overhaul", "refactor entire project", "transform", "rebuild in [language]", "spec-driven", or describes any large-scale project transformation that requires planning before coding. Also triggers on Chinese keywords: "改造", "重写", "迁移", "重构", "大规模", "规范驱动". Performs full project analysis, task decomposition, documentation generation, progress tracking setup, and task-specific sub-SKILL creation before any development begins.

0 Updated today
1530snosecount886