tinyspecv0.0.9
Docs

Specs you write,
AI that builds

Create structured, human-readable specifications in plain Markdown. Refine them with AI, track implementation progress, and amend the plan as requirements evolve. No generated artifacts, no ceremony — just specs that live in your repo and make sense to humans.

$cargo install tinyspec
GitHub

Zero ceremony, full clarity

No frameworks to learn, no agents to configure, no generated file trees. Just a single binary, plain Markdown specs, and a CLI that gets out of your way.

Human-readable specs

Write structured specifications in plain Markdown with Background, Proposal, and Implementation Plan sections. No generated multi-file artifacts — one file per feature, readable without tooling.

AI-assisted, not AI-dependent

Refine specs and implement plans with Claude Code slash commands. But your specs always work without AI — read them, edit them, and track progress from the terminal.

Living plans that evolve

Check off tasks as you go, amend specs by adding new tasks as requirements change, and track progress across all your specs with a real-time TUI dashboard.

Multi-repo support

Map application names to repository paths. Specs can reference multiple codebases, and tinyspec resolves the paths automatically.

Templates

Create custom spec scaffolds with variable substitution. Standardize how your team writes specs with reusable templates.

Get started in minutes

Install tinyspec, create a spec, and let Claude Code handle the rest.

1

Install tinyspec

$ curl -fsSL https://tinyspec.dev/install.sh | sh
2

Initialize in your project

$ tinyspec init
3

Create a new spec

$ tinyspec new my-feature
4

Refine with Claude

Claude Code
> /tinyspec:refine my-feature
5

Implement the plan

Claude Code
> /tinyspec:do my-feature

Need to adjust the plan? Run /tinyspec:refine again to iterate, then /tinyspec:do to continue implementing.

How tinyspec compares

Other tools add frameworks, agents, and generated artifacts. tinyspec keeps it simple. View the full comparison table

vs OpenSpec

OpenSpec generates four files per change and requires an AI agent for its core workflow. tinyspec gives you one Markdown file and a standalone CLI.

vs SpecKit

SpecKit imposes formal ID schemes, constitutional governance, and Python dependencies. tinyspec keeps specs simple and readable.

vs BMad METHOD

BMad installs dozens of agent and workflow files into your project. tinyspec adds one directory and stays out of your way.

vs GSD

GSD generates XML tasks optimized for LLMs, not humans. tinyspec specs are plain Markdown that anyone can read and amend.