Reusable markdown templates for spec-first development. Drop them into any project, fill in the blanks, and align your team before a single line of code is written. Works with any stack, any team size, and any AI coding assistant.
# Copy all templates into your project
cp -r templates/ docs/specs/
# Or grab just the one you need
cp templates/feature-spec.md docs/specs/my-feature.mdThen open the file and fill in each section. Commit the spec to your repo before writing any implementation code.
Define the goal, non-goals, acceptance criteria (Given/When/Then), and edge cases for a feature. Use this before starting any new feature work to align your team and give your AI assistant a clear target.
Document an endpoint's method, path, request shape, and response shape — successes and errors. Based on the OpenAPI mindset but lightweight enough to live in a markdown file.
Capture table columns, types, constraints, indexes, and a migration plan in one place. Prevents schema drift and makes code review easier.
Not sure where to start? The Spec Generator at spec-coding.dev walks you through each field interactively and produces a filled-in spec you can copy straight into your repo.
These templates are designed to be AI-readable. When you give an AI assistant a spec file instead of a vague prompt, you get:
- Code that matches what was agreed on — no surprise features
- Field names and shapes that match your spec exactly
- Edge cases handled because they were written down first
Setup:
- Drop
CLAUDE.mdinto your project root to configure Claude Code - Drop
.cursorrulesinto your project root to configure Cursor - Reference a spec file in your prompt: "Implement the spec at docs/specs/my-feature.md"
MIT — free to use, copy, and adapt.
Built by spec-coding.dev — the home of spec-first development.