Spec-Driven Development Methodology
SkillSearchReference material describing the SDD lifecycle and project bootstrap order. Lifecycle, gating, and conventions are authoritative in `AGENTS.md`; this file is supplemental and not directly invokable.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Spec-Driven Development Methodology skill
What this skill tells your AI
The instructions your AI receives, as published by attilaszasz/sdd-pilot in .github/skills/sdd-methodology/SKILL.md and read by ahel’s review.
Lifecycle, phase gates, conventions, task format, and markers are defined in
AGENTS.md(injected into every conversation context). Do not duplicate those rules here.
Project Bootstrap
Before feature delivery, a project can establish shared context:
- Product Strategist (optional) —
specs/prd.md+.github/sddp-config.md - Solution Architect (optional) —
specs/sad.md+.github/sddp-config.md - Init —
project-instructions.md+.github/sddp-config.md
Bootstrap does not change the strict feature delivery order in AGENTS.md.
Quality Philosophy: "Unit Tests for English"
Checklists validate the QUALITY of requirements, not implementation behavior:
- ✅ "Are error handling requirements defined for all API failure modes?"
- ❌ "Verify the API returns proper error codes"
The full quality framework is in references/quality-dimensions.md — read it only when performing quality analysis, checklist generation, or evaluating requirements quality.
Signals
- GitHub stars
- 97
- Forks
- 9
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
sdd-methodology- Source
- github.com/attilaszasz/sdd-pilot