Coding · v2.0.0

SaaS Scaffold Spec

A spec writer that exists so Grok Build does not gold-plate. You answer: audience, one job-to-be-done, must-have screens, and what is explicitly out of scope. It emits a tight app brief — pages, auth yes/no, entities, empty/error states, visual direction — and a live preview of the prompt you will paste. Phase 1 is defined as ‘shippable in one sitting.’

diff.ghost · 4,293 votes · 25,664 score · 12,785 opens

#spec#saas#scaffold#phase-1

Spec

Build SaaS Scaffold Spec — a spec writer whose output is a Grok Build prompt, not a PRD graveyard.

PRODUCT
A short interview that compiles into a single copyable Build prompt. The compiler’s job is subtraction: it fights gold-plating.

INTERVIEW (one page, not a 12-step wizard)
Fields, all required except notes:
- Working title
- Audience (one sentence)
- One job-to-be-done (one sentence, starts with a verb)
- Must-have screens (tag input, 2–6)
- Auth: none / magic-not-now (local only) / accounts required
- Entities (tag input)
- Explicitly out of scope (textarea; placeholder “mobile native, admin impersonation, CSV import…”)
- Visual direction (chips: phosphor terminal, paper editorial, dense dashboard, playful mono — user can type their own)
- Notes (optional)

COMPILER OUTPUT
A prompt with these headings, always in this order:
PRODUCT / WHO / JTBD / SCREENS (named, with purpose) / DATA (entities + persistence) / EMPTY ERROR LOADING / VISUAL / OUT OF SCOPE / ACCEPTANCE (3–5 bullets the builder can tick).
Phase-1 cut line is injected: “If a feature is not named in SCREENS or DATA, do not build it.”

SCREENS
1. Interview
2. Preview — the compiled prompt in a spec sheet. Copy button. “Tighten” pass that removes adjectives and duplicate screens.
3. History — last 8 specs, reload into the interview.

RULES
- If screens > 6, block compile with “cut two or this will not ship in one sitting”.
- If out-of-scope is empty, compile still runs but paints a warning: “ unbounded scope; add at least one cut”.
- Ban in output: seamless, unlock, elevate, robust, end-to-end, revolutionary.

VISUAL
Spec-sheet. Numbered headings, 1px rules, mono labels. The preview should look like a document someone would paste, not a chat bubble.

OUT OF SCOPE
Generating the app itself, Figma export, multiplayer spec editing.

ACCEPTANCE
- Compiling a “personal CRM, local only, 3 screens” produces a prompt that includes empty states and a cut line.
- Copy puts the exact preview text on the clipboard.
- Mobile: interview stacked, preview below, copy button 44px.