A Claude skill that keeps your AI coding tools from contradicting each other. Generates requirements.md, design.md,...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health 42/100. no security policy. 8 open issues make this testable, but not something to trust blind.
AI Agent
Multiple
Model
Claude
Fastest way to find out if Spec-Driven-Development belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
# Visit: https://github.com/FredAntB/Spec-Driven-DevelopmentRun this first. You will know quickly if the workflow earns a permanent slot.
# No automated removal — visit https://github.com/FredAntB/Spec-Driven-DevelopmentNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ spec-driven-development/ ← installs here └─ settings.json
A Claude skill that keeps your AI coding tools from contradicting each other. Generates requirements.md, design.md, and tasks.md before any code is written — then creates matching config files for Claude Code, Cursor, Copilot, Windsurf, and Aider.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: May 23, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.