Spec book

Your app's spec, as a book you can mark up.

A Claude Code plugin. Every screen, for every role, as phone mockups beside the requirements they prove. Pin notes where something is wrong, and Claude revises the spec. Mark a section Ready, and Claude builds it.

$ claude plugin marketplace add jsonxr/claude-plugins
$ claude plugin install specbook@jsonxr

Then, in any project, run /specbook to lay out a book for the whole app.

2.3 Sign in with a code

Drafting · 2 changes
  • ONB-8KABA wrong code reads "That code didn't work", whatever was wrong with it. unit ✓e2e ✓
  • ONB-J7ALFive wrong guesses burn the code, and each guess waits longer. unit ✓
  • ONB-HKY4Below the code field: "Check your spam folder." new

Resend should wait 30 seconds, not 60.Ann

Say which address the code went to.You

One loop, from idea to tested code

The book is where you and Claude agree on what the app does. Nothing is built until you say a section is ready, and nothing Claude changes sticks until you accept it.

  1. Design

    /specbook:design writes chapters, requirements and a mockup of each screen for each role, with you.

  2. Mark it up

    Press Comment and click the exact spot: a field, a button, a sentence. Your note pins there.

  3. Revise

    Press Revise. Claude works through every note with you, edits the spec, and answers notes that change nothing.

  4. Accept

    Each change waits under review, next to the wording before it, until you press ✓ Accept or pin another note.

  5. Build

    Mark a section Ready and press Build. Claude builds it and ties each requirement to the tests that prove it.

What the book holds

One scrollable document for the whole app, kept in your repository beside the code it describes.

The app in the order a person meets it
Signing up, the first screen, each tab and what it leads to. Not the order of the code, and nothing hidden behind tabs.
Every screen for every role, side by side
An admin, a member and a visitor each get their own frame, so a difference between them is visible at a glance.
Requirements with ids that never change
Short, testable sentences with stable ids. Tests name the ids they prove, and the book shows which ones pass, beside the real screenshots.
A history of what you accepted
Each item keeps the versions you accepted before, and every build adds a plain-words entry to the changelog.
Decisions, written down once
What was settled or rejected stays in the book, so Claude doesn't propose it again.
Your data, in your project
The book is a folder of JSON and HTML in your repo. The plugin holds only the code that reads it.

The commands

Type them in Claude Code, or just ask: each one also starts when what you ask for matches it.

CommandWhat it does
/specbookCreates a book for the project and lays out the whole app, or serves the one it has.
/specbook:openOpens the book in your browser, starting its server if it isn't running.
/specbook:designWrites or revises a part of the book with you: chapters, requirements and mockups.
/specbook:reviseWorks through the notes you sent with Revise, and edits the spec from them.
/specbook:buildBuilds the sections marked Ready, proves each requirement with tests, and collects the evidence.
/specbook:shareGives you a link to the live book for collaborators. /specbook:share stop ends it.