tinyspec

tinyspec is a small framework for writing specs that language models implement. It integrates with Claude Code and gives a structured loop: create a spec, refine it with Claude, then work through the implementation plan. It sits at the lightweight end of spec-driven-development: one Markdown file per feature, one directory added to the project, one binary.

Repository snapshot (GitHub API, 2026-11-20)

ItemDetail
Reponmcdaines/tinyspec, Rust, MIT
Created2026-02-16
Activitylast push 2026-03-18; latest release v0.0.9 (2026-02-19)
Size7 stars, 2 forks
Installcargo install tinyspec (crates.io) or build from source

A very young, very small project. Treat it as a pattern to borrow or try, not an established ecosystem.

How it works (README and tinyspec.dev)

  1. Init: tinyspec init installs three Claude Code skills in .claude/skills/ and sets up shell completions: /tinyspec:refine, /tinyspec:do and /tinyspec:task. tinyspec init --force updates them after an upgrade.
  2. Create: tinyspec new my-feature writes a timestamped Markdown file in .specs/ with sections for Background, Proposal, Implementation Plan and Test Plan. group/name (for example v1/my-feature) puts it in a one-level group; names are unique across groups.
  3. Refine: /tinyspec:refine my-feature has Claude read the spec, ask clarifying questions and build the plan as task groups (A, B, C) with subtasks (A.1, A.2).
  4. Implement: /tinyspec:do my-feature works through each group in order, ticks subtasks off and commits after each group. /tinyspec:task my-feature A.1 does one task.
  5. Track: tinyspec status and tinyspec dashboard, a terminal dashboard that watches .specs/ and shows specs sorted by status with completion percentages.
  6. Amend: re-run refine to change the plan as requirements move, then run do again.

Other features: multi-repo specs (application names in the spec front matter resolve to folders through ~/.tinyspec/config.yaml, managed with tinyspec config set|list|remove), and Markdown templates with variable substitution (a repo-level .specs/templates/ takes precedence over the user-level one). Specs stay readable and editable without AI.

Comparison with other spec-driven tools

tinyspecSpec KitOpenSpecBMad MethodGSD CoreKiro
LicenceMITMITMITMITMITProduct from AWS
Written inRust, single binaryPython 3.11+ and uvTypeScript, Node.js 22.20+Python and Node.js, installed as skillsJavaScript, Node.js installerIDE, CLI and web
Stars (2026-11-20)7about 139.6k (2026-09-30)75,31555,56811,720 (original repo 64,126)n/a
Artefacts per featureOne Markdown fileSeveral: constitution, spec, plan, tasksFour per change: proposal.md, specs/, design.md, tasks.mdBriefs, specifications and architecture; the README names no filesSTATE.md, CONTEXT.md and per-phase plansThree: requirements.md (or bugfix.md), design.md, tasks.md
FlowRefine, then doConstitution, specify, plan, tasks, implement, convergeExplore, propose, apply, archiveClarify, plan, build and verify, learn and adjustDiscuss, plan, execute, verify, shipRequirements, design, tasks
Governance or rolesNoneConstitution of project principlesSpecs archived and merged per changeSpecialised product, architecture, UX, dev and test perspectivesFresh-context subagents per stepNot covered here
Agent supportClaude Code skillsMany agents; Copilot is the default30+ toolsTools that support skillsClaude Code, Codex, Copilot, Cursor, OpenCode and moreKiro itself
ScopeOne feature, one checklistFormal stages per featurePer-change specs with an archive and a living spec setWhole delivery loop, with modules for testing, games and moreMilestones and phases with context managementIDE-integrated specs
Human-firstPlain Markdown, usable without AINot statedPlain Markdown scenarios you review before codingDecisions kept explicit for the humanVerify step walks through what was builtIDE-driven

How to read the table: figures come from each project’s own README and GitHub API on 2026-11-20, except Spec Kit and Kiro, which come from this vault’s notes (Spec Kit, Kiro, spec-driven-development). Stars measure popularity, not quality. tinyspec.dev describes the other tools as heavier than itself (OpenSpec’s four files, Spec Kit’s governance and Python dependency, BMad’s many files); the table records what their own pages say instead.

Where it fits

  • Choose tinyspec for a solo developer or small team on Claude Code who wants a readable checklist per feature with little ceremony and a progress view.
  • Choose Spec Kit when a team wants shared principles, several agents and formal stages.
  • Choose OpenSpec for per-change specs with an archive step and wide tool support.
  • Choose BMad Method for a whole-delivery method with roles and modules, or GSD Core when context rot across long sessions is the main problem.
  • Choose Kiro when the workflow should live inside an IDE.
  • No benchmark or independent review compares these tools, so which one gives better results is not established.

Same name, different project

A Spec Kit community extension is also called “TinySpec” (Quratulain-bilal/spec-kit-tinyspec). It adds a lighter workflow for small changes inside Spec Kit and is a different project from nmcdaines/tinyspec. Its page was not opened.

Sources