Comparison
Storybloq and spec-kit: complementary, not competing.
Both put project context in the repo. Both target AI coding agents. They solve different problems at different layers. Spec-kit handles spec-driven feature delivery; Storybloq handles state-driven session continuity. Use either, or stack both.
What spec-kit is
GitHub's spec-first delivery framework.
GitHub's spec-kit is a spec-first delivery framework. At the time of writing it has 95,000+ stars, ships under MIT, and is actively maintained from github/spec-kit.
The workflow is linear and per-feature. /speckit.constitution establishes project principles. /speckit.specify captures requirements as User Stories with priorities (P1, P2, P3), Functional Requirements with FR-001 IDs, and Given/When/Then acceptance scenarios. /speckit.plan documents tech stack and architecture. /speckit.tasks breaks the plan into actionable items. /speckit.implement executes them.
Each new feature gets its own specs/###-feature/ folder with templated artifacts: plan.md, research.md, data-model.md, contracts/, tasks.md. Specifications are the executable artifact; code is generated from them.
Source: github.com/github/spec-kit.
What Storybloq is
A state-driven operational layer.
Storybloq is a state-driven operational layer for AI coding projects. Project state lives in a .story/ directory inside your repo, tracked by git, readable by any AI client through MCP tool calls.
Primitives include tickets (typed work items with status, phase, dependencies), issues (discovered problems with severity and impact), handovers (narrative session-boundary documents), and lessons (graded patterns the project has learned, with reinforcement counts). The /story skill loads accumulated state at the start of every session. Autonomous mode runs full PICK_TICKET, PLAN, PLAN_REVIEW, IMPLEMENT, CODE_REVIEW, FINALIZE, COMPLETE pipelines with cross-model review built in.
A native Mac app visualizes the project state live as Claude works.
More: Mac app · CLI and MCP · Install.
Side by side
Same camp, different layers.
| Aspect | spec-kit | Storybloq |
|---|---|---|
| Bet | Spec-driven (spec to code) | State-driven (state evolves with work) |
| Primary unit | Per-feature folder | Project-wide typed artifacts |
| Continuity primitive | Constitution + per-feature specs | Handovers + reinforced lessons |
| Time orientation | Forward (delivery) | Bidirectional (continuity) |
| Workflow shape | Linear pipeline | State machine + accumulation |
| Multi-AI review | Community extensions | Built-in (codex-bridge + lenses) |
| Native dashboard | None (CLI + web UI) | Mac app |
| Distribution | Python CLI + extensions ecosystem | npm CLI + Mac app + MCP server |
| Backed by | GitHub | Independent |
How they stack
Designed for different layers.
The two products are architecturally complementary. Spec-kit handles spec-to-code for a new feature: write the spec, generate the implementation. Storybloq handles session-to-session continuity across many features: track what is happening, preserve handovers, accumulate lessons.
A typical stacked workflow: a developer runs /speckit.specify to capture requirements for a new feature, then /speckit.plan and /speckit.tasks to break it down. At the end of the session, Storybloq writes a handover capturing what was done and what is next. The next session starts by reading the handover, picks up the in-progress feature, and continues. Spec-kit's per-feature artifacts and Storybloq's project-wide state survive together.
A deeper integration is scoped under ticket T-323: read spec-kit's tasks.md as Storybloq tickets, surface spec-kit's constitution as a parallel governance doc, route /speckit.implement through Storybloq's autonomous mode. Until that ships, both products coexist with no conflict.
Which should I use
A short decision guide.
- 01
You want structured spec discipline for each new feature.
Use spec-kit.
- 02
You want session-to-session continuity, multi-AI review, and a native dashboard across the whole project lifecycle.
Use Storybloq.
- 03
You want both.
Stack them. They were designed for different layers.
Try it on your next project.
Storybloq is free, local-first, and works alongside spec-kit or on its own.