Back to directory

Spec-Driven-Development

A Claude skill that interviews you before any code is written and generates a shared requirements, design and task plan, then creates matching configuration files so Claude, Cursor and Copilot stop contradicting each other.

Spec-Driven-Development

This skill addresses AI coding tools working from no shared source of truth, each filling gaps in an ambiguous request with its own assumptions. Before any code is written, it interviews the developer and generates three files: requirements.md with traceable, testable requirements, design.md describing how the system will be built, and tasks.md listing what to build next in order, each task linked back to its requirement.

It then creates matching configuration files for Claude Code, Cursor, Copilot, Windsurf and Aider, so every tool reads from the same plan. Starting a conversation with a prompt such as wanting to begin a new project, or already having a codebase with no specs yet, walks through a short set of questions and produces the spec files without further configuration.

It installs as a Claude skill file or a Claude Code plugin, and is written in Python under the MIT license.

More in Agent skills

See all 581
  • Provenance gate

    github.com

    A deterministic authorization gateway that sits between an AI agent and its tools, tracing where each parameter of a side-effect call came from, and blocking the call or asking a human when the source does not check out.

  • A markdown framework of system rules that restates Isaac Asimov's Four Laws of Robotics as a set of prioritized loss calculations for large-language-model agents to follow, published as a discovery file for agents and crawlers to read.

  • Vitruvius

    github.com

    An engineering research agent that runs a discover, read, synthesize, verify and review loop over technical questions, reading sources directly rather than inferring from titles, and publishing its own scored verifier benchmark, weaknesses included.