n2bnapkin → blueprint

Open source · MIT · Runs inside your AI coding agent

Vibe code the build.Blueprint the product first.

n2b turns a raw product idea into an investment-ready blueprint — market research, feature specs, architecture, and a handoff package any dev team or AI build tool can run with. It deliberately writes no code.

Get the blueprint
  • Claude Code
  • Cursor
  • OpenCode
  • Codex · experimental
.n2b/
├─ BRIEF.md · validated project brief
├─ features/ · research, personas, journeys, feature list
├─ specifications/ · one spec per feature, verbatim ACs
├─ architecture/ · recommended stack + DB schema
└─ exports/ · jira · speckit · lovable-pack · …

Blueprint complete — ready to hand off

Project
YOUR IDEA
Scale
1 INTERVIEW : 1 PRODUCT
Sheet
N2B-001
Path A

“I’m about to vibe code.”

Lovable, v0, Bolt, and Cursor build fast — from whatever you give them. Run n2b first and hand them a blueprint instead of a vibe: researched features, real acceptance criteria, a data model. Stage 5 even exports a per-feature prompt pack for your tool of choice.

See the prompt-pack exports →
Path B

“I have an idea, but no team.”

No PM, no architect, no researcher? The pipeline plays those roles — interviewer, market researcher, spec writer, architect. One interview in → a full feature list, per-feature specs, recommended architecture, and a database schema, before dev kickoff.

See what the blueprint contains →
the 70% wall

Fast, until it isn’t.

AI build tools get you 70% of the way in an afternoon. Then the skipped groundwork surfaces: no research, no feature definition, no data model, no acceptance criteria — and the build starts to drift. The fix isn’t better prompting. It’s doing the front half of the lifecycle before the first line of code.

Five commands. One blueprint.

Same pipeline in every runtime
  1. 01 · s1-init

    Intake

    A structured interview about your idea — it asks until it’s confident, not until a form is filled.

    → BRIEF.md
  2. 02 · s2-define

    Define

    Market research, personas, journeys, a prioritized feature list — audited for completeness.

    → features/
  3. 03 · s3-specify

    Specify

    Every feature in implementation-ready depth, with verbatim acceptance criteria and a hard quality gate.

    → specifications/
  4. 04 · s4-architect

    Architect

    Live tech research → a recommended architecture with documented alternatives, plus a database schema.

    → architecture/
  5. 05 · s5-export

    Export

    The finished blueprint, rendered for whichever team or tool builds it. Repeatable, fidelity-gated.

    → exports/

Each stage passes a quality gate before the next will run. When stage 4 passes:blueprint complete.

Invoked as /n2b:s1-init in Claude Code · /n2b-s1-init in Cursor and OpenCode · $n2b-s1-init in Codex

Works where you already work

One install. Your agent, your subscription.

n2b installs project-locally into whichever AI coding agent you already pay for. No new account, no metered credits, no SaaS in the middle — the same pipeline, translated to each runtime’s command format.

Run the installer with no flag and a picker asks which runtime to install; the --all flag installs every runtime.

One interview in. Every build tool out.

Every export is checked against the blueprint by a fidelity gate before it’s accepted — counts reconciled, acceptance criteria carried verbatim.

n2b does not build your product.

that’s the feature

The blueprint you approve is the blueprint your builder receives — no mid-project spec drift, no lock-in, no metered credits. MIT-licensed, zero npm dependencies, everything is Markdown. It runs on the AI coding subscription you already have.