VibeSpec

AI PRODUCT PLANNING

Describe your idea.
See the plan before you build.

VibeSpec is a free, open-source AI product-planning plugin for Claude and Codex.

Create a connected product plan. Review it together, then hand the file to AI with your next request.

Start for freeFree templates

Choose booking creation, changes, or live status to explore the actual plan.

TRY A REAL PRODUCT PLAN

Meeting Room Booking

SOT

Example requestPlan an internal meeting-room booking app. Define how bookings, changes, and conflicts should work.

Pick a feature, then explore the tabs.

R2 Booking management F3

Create booking

Book a room, time, and attendees. Block conflicts and track notification delivery separately.

Acceptance criteria

  • Only one overlapping booking for the same room is confirmed.
  • Missing fields, excess capacity, or unavailable hours prevent confirmation.
  • Notification failure neither duplicates nor cancels an already confirmed booking.
Detailed scope

F3:0 Pick a room and time slot

An employee picks an operational room and start/end times in the company time zone. Availability uses [start, end) intervals so adjacent bookings are allowed; conflicts are checked again at confirmation.

  • An existing 09:00–10:00 booking blocks 09:30–10:30 but allows 10:00–11:00.
  • Past times, end≤start, closed hours, or a maintenance window cannot be confirmed.
  • Two simultaneous confirmations for the same slot persist only one booking; the other retains its input and receives alternative availability.

F3:1 Attendees and capacity

The booker selects attendees from the active staff directory. Unique attendees including the booker are compared with room capacity; external guests are outside the initial scope.

  • Selecting the same employee twice counts that person only once.
  • Exceeding room capacity including the booker blocks confirmation in both the UI and server.
  • Inactive employees or external email addresses are rejected with an explanation and are not saved as attendees.

F3:2 Confirm booking and track notifications

The server rechecks permissions, conflicts, and the input revision, then confirms once using booking_id and request_id. Attendee delivery is queued only after commit, with its status separate from booking status.

  • Retrying one request_id returns the existing booking_id rather than creating a second booking.
  • A simultaneous conflict preserves the form and returns to time selection without a confirmation notification.
  • After persistence succeeds, a delivery outage shows confirmed booking plus failed/retryable notification status.
  • The first successful confirmation records E1 once per booking_id; failures, edits, and retried responses do not count as new confirmations.

YOUR NEXT AI REQUEST

Change one feature.
See what to review with it.

“Block cancellations within 30 minutes of a booking.” That request needs the existing rule and its connected screens. Attach your reviewed plan so AI has the scope of the change.

The rule in the published plan

F4P10 · P11

View / change bookings

Employees review their bookings and change or cancel only before the start. Other people’s bookings and concurrent edits remain protected.

Acceptance criteria to check

The booker can change or cancel a future booking and see the latest list state.

Example change request with the SOT attached
Use VibeSpec to update F4 in the attached meeting-room SOT. Block changes and cancellations within 30 minutes of the booking start. Review the connected screens, flows, and acceptance criteria. Preserve existing feature IDs.

WHY VIBESPEC

Review the same plan.
Decide the next change together.

A convincing screen can still leave ownership and exceptions undefined. Before requesting code, review the same plan with your team and identify the open decisions and scope of the change.

01

See the connected scope

Requirements, features, screens, and user flows stay in one SOT, so you know which context belongs in the next AI request.

02

Change only what needs changing

Review what a change touches across features, screens, and flows, then ask AI for the scoped update you actually need.

03

Check whether a KPI can be measured

KPI Measurement Check shows missing evidence and decisions, then provides a handoff request for resolving them with AI.

HOW IT WORKS

Create one standard.
Review it. Hand it to AI again.

  1. 01

    Start with an idea or template

    Describe the product you want to build or begin with a real-world template.

  2. 02

    Connect the plan

    Create one SOT with a PRD, feature specs, information architecture, and user flows.

  3. 03

    Review the working source

    Use the HTML viewer to inspect the screens and connections, then make the needed edits.

  4. 04

    Hand it to AI again

    Attach the updated SOT to Claude or Codex for the next scoped request.

START IN CLAUDE OR CODEX

Turn your own idea
into a first product plan.

Install the plugin, then paste this request into Claude or Codex. Replace the example with the workflow your team needs.

See Claude and Codex installation

SOT JSON is the planning source. Generating and validating HTML requires an environment that can run Node.js.

Example first request after installing the plugin
Use VibeSpec to plan a meeting-room booking system for our team. First tell me which artifacts you can generate and validate in this environment. Ask about employee and facilities workflows, overlapping bookings, changes, cancellations, and notifications. Save the agreed plan in the working folder.

LIVE PRODUCT DEMOS

See VibeSpec now,
without downloading anything.

Explore work under review versus release scope, an unresolved KPI decision, and a measurement-ready example in the latest public demos.

01 · CHANGE REVIEW

Compare work under review with release scope

In Neighborly, the review workspace includes proposed work while the integrated release view keeps only the approved scope.

Open change-review demo

02 · OPEN KPI DECISION

Turn an open KPI into the next AI request

See the CRM measurement gap, the decision it needs, and the handoff request that applies it through Claude or Codex.

Open KPI decision demo

03 · MEASUREMENT READY

Inspect a plan ready for measurement

See how the WeekChef demo connects KPI evidence with its events, features, and screens.

Open ready-plan demo

START WITH A FREE TEMPLATE

Start your own product
context with a free template.

Explore the three latest system planning templates. Each includes a free PRD, editable SOT, and HTML planning viewer—not a ready-to-run application.

Browse all 112 free templates

FAQ

Before you start

What is VibeSpec?

VibeSpec is a free, open-source AI product-planning plugin for Claude and Codex. It turns product ideas into connected PRDs, feature specs, information architecture, and user flows that you can review in an editable SOT and hand back to AI for the next scoped request.

Does VibeSpec build the application?

VibeSpec creates connected planning files and an HTML viewer with a PRD, feature specs, information architecture, and user flows. Hand the reviewed plan to a developer or coding agent for implementation.

Is VibeSpec free?

VibeSpec is free and open source under the MIT license. The planning templates and live demos on this site are also free. Claude or Codex usage is subject to the host service’s own pricing.

OPEN SOURCE · FREE TO USE

Hand your product context
to AI with your next request.

VibeSpec is free and open source. Start with a template or install the plugin to create the SOT for your own product.

Free templatesView the plugin on GitHub