Featherspec

Spec-driven development that works in Claude Code _and_ GitHub Copilot — from the same files.

No CLI. No install. No dependencies. Markdown and folders.

A chat forgets. FeatherSpec doesn't.

You describe what you want, your agent turns it into a spec with testable acceptance
criteria, then into a plan of baby steps — and only then writes code. Spec, plan, decisions
and progress all live on disk as Markdown in your repository, so the next session, the next
teammate, and the next tool pick up exactly where you left off.

Thirteen /sdd-* commands drive that loop — identical in Claude Code and GitHub Copilot,
because both tools execute the same files.

Tracking work in Jira or GitHub Issues? One wizard answer links every spec to a ticket and every
status move to a transition — through the tracker access your tool already has, with no tracker
knowledge inside FeatherSpec. Solo developers answer none and never see it.

Start in two minutes

*(These three steps are the greenfield path — adopting an existing repository? Jump to
Already have a codebase?.)*

1 · Get the template

Click Use this template on GitHub — or clone it:

The clone brings this repository's commit history along with a remote pointing back here. For
your own project you want neither: delete the .git folder (rm -rf .git, or
Remove-Item -Recurse -Force .git in PowerShell) and run git init.

Have Node.js? Then degit saves you that cleanup — it downloads only the current file
state, so there is no history and no .git folder to detach in the first place:

2 · Open it in your assistant

Claude Code

CLAUDE.md imports AGENTS.md at session start, so the rules are always loaded. Type / and
the sdd- commands are there.

GitHub Copilot (VS Code)

Open the project folder itself — not a parent folder, or the slash…