Claude Code Plugin

You had the meeting. Everyone aligned.

A week later, nothing was buildable.

Visionaire turns that week into one afternoon.

One 1–3 hour session closes that gap: a product brief, user flows, architecture doc, and 15–50 executable feature specs. Your developer starts Monday. Not “soon.”

Start my spec session — $297 $297 early access — first 100 builders  ·  Becomes $447 after See a sample spec  →
One payment. Keep it forever. Runs locally. No telemetry. 30-day guarantee.
BRIEF.md
UIUX.md
F-003-auth.md
1# Product Brief: TaskFlow Pro
2
3## Problem Statement
4Engineering teams lose 23% of sprint capacity to rework caused
5by unclear requirements. Current tools (Jira, Linear) track tasks
6but don't enforce specification quality before work begins.
7
8## Target Users
9Primary: Engineering managers at 20–200 person companies
10Secondary: Senior engineers who define technical requirements
11
12## Success Criteria
13- [x] A developer can implement any feature spec without a follow-up
14- [x] Zero ambiguous acceptance criteria per feature
15- [x] Architecture decisions documented before code review begins
16
17## Stage Gate: Brief Review
18✓ Problem is specific and measurable
19✓ Users are named with context
20✓ Success criteria are testable
21→ Ready for Market Validation

Your team spent a week in meetings. You have notes. Still no specs.

The traditional process — brainstorm, align, document, revise — takes days before a developer touches anything. And the output is still a rough doc that someone has to turn into real specs. Visionaire replaces that entire cycle with a single afternoon conversation that ends with everything your developer needs to build.

The meeting that produces nothing buildable
Two senior people. Half a day. $560–$960 in salary. The output: a whiteboard photo and a follow-up doc nobody finishes. Specs take another week.
Most bugs aren't code bugs
They're missing requirements. A developer can't implement a confirmation dialog that wasn't in the spec. It ships. Users lose work. You schedule a sprint to fix it.
Specs that don't know what you already built
Every other spec tool assumes a blank canvas. If you have an existing codebase, a new feature planned in isolation gets bolted on instead of built in.

If you're building serious software — not a demo, not an LLM wrapper — you need specs a developer can open Monday morning. Not notes.

GATE

Most bugs aren't code bugs — they're missing requirements. After each phase, a specialized reviewer agent validates the output before you advance. A product design consultant reviews every user journey and catches under-specified interactions before a developer sees the spec. Nothing moves forward until it clears.

The spec is the product.

You think you've thought it through.

You've written it down. You can see the system in your head. The AI should be able to build from this.

Then it does. And it builds something that is technically correct and completely wrong — because the gaps in your spec weren't missing words. They were missing questions. And nobody asked them.

"I wanted something that would interview me — ask follow-up questions based on what I actually said, surface what I didn't know I knew, and close every ambiguity before AI begins to build."

— Robert Evans

One conversation. 15–50 executable specs. Everything your developer or AI agent needs to start Monday.

No forms. No templates to fill out. Just describe what you're building — the right questions come to you. At $20 per spec, it's less than any PM you'd hire. A product design consultant reviews every user journey before you're done, catching the requirements nobody thought to write.

Progressive clarity workflow
Each phase feeds the next. The Brief informs UX. UX informs architecture. Architecture constrains features. No disconnected docs, no orphaned decisions. The system builds coherence by design.
You approve the outline first
Before any document is written, you review a structured outline. Direction is confirmed before content is generated. Nothing runs ahead of your judgment.
Assumptions tracked across all phases
Every assumption surfaced in Phase 0 is explicitly tracked through every downstream phase — validated, challenged, or set aside. Nothing is silently inherited.
LLM-ready output
Every artifact is structured for direct handoff to an implementation agent. The spec feeds the builder. No translation layer. No interpretation required.
Feasibility review before architecture
Before the architecture interview begins, the agent flags any UX requirement that's technically infeasible or has a meaningfully cheaper alternative. You decide before the foundation is laid.
Journey coverage check
Before features are written, every user journey from your UX spec is mapped to at least one feature. Gaps surface before specs — not after implementation starts.
Market validation built in
Optional web research phase. The agent researches market size, competition, timing, and acquisition channels — every claim sourced. GO, RECONSIDER, or NO-GO before you invest a week in design.
Works on what you already have
Adding a feature to an existing app? Visionaire reads your codebase first — architecture, current user journeys, existing patterns — before recommending anything. Features fit in. They don't bolt on.
Auto-resume orchestration
The orchestrator records your exact position in orchestrator.json. Close Claude Code, come back tomorrow — /visionaire:start picks up exactly where you stopped.

This is what an implementation agent receives.

Every decision made. Every constraint defined. Every dependency declared. Zero follow-up questions needed.

This is a real Visionaire feature spec — not a template, not a mockup. This is the format your team works from.

BRIEF.md
F-003-auth.md
ARCHITECTURE.md
1# F-003: User Authentication
2
3Type: Core Feature · Status: Draft
4Journey: New User Registration and Login
5
6## Scope
7In: Email/password authentication with session management
8Out: OAuth, SSO, 2FA — defined in F-007
9
10## User Interaction
11Pre: Unauthenticated visitor on registration or login screen
12Post: Authenticated session established, email verified
13Error: Invalid credentials → inline error, system state preserved
14
15## Acceptance Criteria
16Given unregistered user submits email + password (≥ 12 chars)
17When registration form is submitted
18Then account is created and verification email is queued
19
20Given user submits incorrect credentials on login
21When login is submitted
22Then error distinguishes "not found" from "wrong password"
23
24## Dependencies
25F-001 (database schema) · F-002 (email service)
26
27Stage Gate: ✓ APPROVED — ready for implementation

Less than one team brainstorm. More useful than a week of meetings.

One payment. No recurring charges. No feature limits. No upsells.

Single User
$297
Early access — first 100 builders
$447 after
Full workflow — all 6 phases
All reviewer agents included
Runs locally in Claude Code
Auto-resume orchestration
Unlimited projects
12 months of updates included
Start my spec session — $297

A team brainstorm costs $560–$960 in salary and produces notes. Visionaire costs $297 and produces 15–50 executable specs, a product brief, a user journey, and an architecture doc. The last team meeting that generated anything this complete probably took a week and cost three times as much.

One payment · Runs locally · No account required · No telemetry · 30-day money-back guarantee

Questions before you commit.

Is Visionaire right for me?

It's a good fit if you're building serious software — something with real users, real architecture, and real consequences if a requirement gets missed. New projects and existing codebases both work. If your developer is waiting on specs, this replaces your next week of meetings.

It's not a good fit if you want a quick prototype or an LLM wrapper spun up in 20 minutes. For that, use Lovable or Replit. Visionaire is for software that has to work.

Does this work with any Claude Code project?
Yes. Visionaire installs as a Claude Code plugin. It works in any repository, any language, any framework. The specifications it generates are language-agnostic markdown files stored inside your repo.
What happens after I buy?
You receive the plugin files immediately. Install as a Claude Code plugin by adding the directory to your workspace. Run /visionaire:start in any project to begin.
Does it require an internet connection?
Yes — Claude Code itself requires an internet connection to run. Visionaire doesn't add any external calls beyond that. No separate account, no telemetry, no data sent to Visionaire servers. Everything stays in your repo. Market Validation (Phase 3) also performs web research, but that step is optional.
What if it doesn't work for me?
30-day money-back guarantee. No questions asked. Email, request a refund, done.
Do future updates cost extra?
No. One purchase includes 12 months of updates. As Visionaire evolves — new phases, improved reviewers, better orchestration — you get every update released within that window at no additional cost.
How long does a session take?
Most sessions take 1–3 hours depending on complexity. You can pause anytime and resume exactly where you left off — the system saves state between phases. There's no rush, no live call, no schedule to coordinate.
I'm a solo developer — is Single User right for me?
Yes. Single User covers one developer across unlimited projects. If you bring on collaborators, contact us for upgrade pricing to Team.

Stop spending a week figuring out what to build.

One afternoon. One conversation. Everything your developer needs to open Monday morning — without a single follow-up question.

Is your current thinking detailed enough for a developer to start without guessing — or would it turn into another week of clarification?

Start my spec session — $297 Equip my team — $997

$297 early access — first 100 builders  ·  Becomes $447 after

One payment. Keep it forever. 12 months of updates. 30-day money-back guarantee. No account required.