1.1 — What is VibeMap?

1.1 — What is VibeMap?

VibeMap turns a one-paragraph idea into a buildable software specification — features, user stories, acceptance criteria, page flows, database schema, and a sprint plan — and then hands the work to your AI coding agent (Cursor, Claude Code, Windsurf, VS Code Copilot) one acceptance criterion at a time.

You stay in charge of the what. VibeMap structures it into a plan. Your AI agent executes the how.

📸 Placeholder: 01-vibemap-flow-diagram.png — high-level "idea → spec → agent → product" diagram.

Who VibeMap is for

VibeMap is built for anyone who can describe what they want to build but doesn't want to keep all of it in their head. That includes:

  • Solo founders and indie hackers who want to ship faster without losing the rigor of a real spec.
  • Product managers who want acceptance criteria, user stories, and personas without writing them by hand.
  • Engineers who want a structured backlog their AI coding agent can actually work through.
  • Non-technical builders who want to direct an AI agent without learning the vocabulary of "user story" and "acceptance criterion."

You don't need to be a programmer. If you can describe what you want a tool to do, you can use VibeMap.

What VibeMap is not

VibeMap is not:

  • An AI coding agent. We give your agent (Cursor, Claude Code, etc.) a clean, sequenced backlog — we don't write your code.
  • A general-purpose project management tool. We're specifically tuned to AI-assisted software development.
  • A hosting platform. You ship your product wherever you like; VibeMap lives alongside.

How it fits together

  1. You write a prompt. A paragraph or two describing what you want to build.
  2. VibeMap generates a spec. Personas, features, user stories, acceptance criteria, page flows, schema, file structure.
  3. You review and edit. Everything is editable. Nothing ships to your agent until you approve it.
  4. VibeMap plans your sprints. It builds a dependency graph across your acceptance criteria and groups them into themed sprints.
  5. Your AI agent picks up work. Via the VibeMap MCP server, your IDE agent claims the next "ready" acceptance criterion, implements it, and submits for review.
  6. You review or let CI review. Mark it passed, the next AC unlocks. Repeat.

The rest of these docs walk you through each step.

Where to go next