Throughspec v1.0 - spec-driven development for Claude Code, now on npm + PyPIRead the docs
WHY THROUGHSPEC

Vibe-coding gets you started.
Structure gets you shipped.

Open-ended prompting drifts. Context cost balloons. Decisions get lost. Throughspec replaces all three with a process that compounds.

Vibe-driven
Open-ended prompts wander off intent with no spec to anchor them.
Every prompt re-scans the repo - context cost grows with the codebase.
Architectural decisions live only in chat history, then vanish.
No predictable layout, so skills and humans hunt for everything.
Throughspec
A frozen SRS gates code - cross-questioning happens before generation.
A compressed context.md replaces N file scans per prompt.
Every decision is appended to design-decisions.md, with rejected alternatives.
One canonical tree - agents and people always know where to look.
01 / SPEC

Spec beats vibe.

Cross-questioning before code generation produces better software than open-ended prompting. So the Kit makes a complete spec a precondition - it refuses to proceed without one, and won’t let you skip the load-bearing questions about users, jobs, success metrics, constraints, and non-goals.

02 / MEMORY

Memory beats re-derivation.

Re-reading source code to reconstruct intent is a recurring token tax that compounds as a project grows. The Kit invests once in condensed, append-only memory files and amortizes that cost across every future prompt - reading a snapshot instead of re-scanning the repo.

03 / STRUCTURE

Structure compounds.

A predictable layout means skills, agents, and humans all know where to look. The Kit refuses to ship freeform - the structure is the product. Consistency early pays back as leverage on every later feature.

Built for four kinds of builder.

The Vibe-Coder

Non-developers building real products through prompting. They get a safe, opinionated workflow that prevents drift - guardrails without ceremony.

The Student

Learning engineering via real projects. They get an auditable trail of why every decision was made, plus a running learnings.md.

The Solo Engineer

Using Claude Code for raw velocity. They get token-efficient context and a reproducible SDLC that holds up across long projects.

The Team Lead

Adopting AI-first engineering. They get a shared structural contract every contributor and agent follows by default.

Stop re-deriving. Start shipping.

Spec-driven. Drift-proof. Token-lean.

Get started ›