Getting Started with VibeMap

Welcome to VibeMap, the AI-powered project management platform that transforms your product ideas into structured, actionable project plans. This guide will help you get up and running in just a few minutes.

What is VibeMap?

VibeMap is an intelligent project planning assistant that leverages AI to help product managers, project managers, and development teams quickly transform product concepts into comprehensive project structures. It automatically generates:

  • Personas: User archetypes that ground feature and story generation

  • Features & User Stories: Feature backlog with detailed user stories

  • Acceptance Criteria: Comprehensive, scenario-based criteria with implementation tags

  • Pages & Components: Suggested routes and reusable UI components

  • Database Schema: Normalized entities, relationships, and SQL scaffolding

  • File Structure: Production-grade app directory and file layout proposals

  • Real-time Streaming: Live progress updates while artifacts generate

Quick Start Guide (5-Minute Tutorial)

Step 1: Create Your Account

  1. Visit VibeMap and click "Get Started"

  2. Sign up using your email or GitHub account

  3. Complete the quick onboarding questionnaire

  4. You'll be redirected to your personal dashboard

Step 2: Create Your First Project

  1. Click the "+ New Project" button on your dashboard

  2. Enter a project name (e.g., "E-commerce Mobile App")

  3. In the description field, provide a free-form description of your product:

Example Description:
"I want to build a mobile e-commerce app where users can browse products, 
add items to cart, make secure payments, and track their orders. Sellers 
should be able to list products, manage inventory, and view sales analytics. 
The app should also have user reviews, wish lists, and push notifications 
for order updates."
  1. Click "Generate Project Plan"

Step 3: Review AI-Generated Structure

You'll see live progress as VibeMap analyzes your description and generates:

  • Personas to anchor requirements in user needs

  • Features grouped by product area (e.g., Authentication, Catalog, Cart)

  • User stories within each feature

  • Acceptance criteria with implementation tags (Frontend, Backend, Database)

  • Pages & components with navigation links by page name

  • Database schema and entities/relationships overview

  • File structure proposals aligned to generated pages/components

Step 4: Customize Your Plan

  1. Edit User Stories: Open a story to update text, acceptance criteria, or priority

  2. Add More Features: Use "Generate Additional Features" for broader coverage

  3. Manage Pages & Components: Review suggested pages/components and refine

  4. Update Personas: Modify or add personas to improve downstream outputs

Step 5: Export and Use

  1. Click "Generate Documentation" when you're satisfied with your structure

  2. Select document types: Project Scope, User Stories, Technical Requirements

  3. Export in your preferred format (PDF, Markdown, or JSON)

  4. Share with your team or import into your preferred project management tool

Your First Project Walkthrough

Let's walk through creating a complete project from start to finish using a Task Management SaaS as an example.

Project Description Input

Project Name: TeamFlow - Task Management Platform

Description:
"TeamFlow is a collaborative task management platform for small to medium teams. 
Users can create projects, assign tasks to team members, set deadlines, and track 
progress. The platform should include time tracking, file attachments, comments 
on tasks, and reporting dashboards. Team leads need approval workflows, and 
admins require user management and billing features. Integration with popular 
tools like Slack and Google Drive is essential."

What VibeMap Generates

1. Feature Breakdown:

  • User Authentication & Management

  • Project & Task Management

  • Collaboration Tools

  • Time Tracking & Reporting

  • Integrations & API

  • Admin & Billing

2. User Roles Identified:

  • Team Member

  • Project Manager

  • Team Lead

  • Administrator

  • Billing Manager

3. Sample User Stories Generated:

**Feature: Task Management**

User Story: Task Creation
As a Team Member, I want to create tasks with titles, descriptions, and due dates, 
so that I can organize my work effectively.

Acceptance Criteria:
โœ… User can create a task with required fields (Frontend, Backend)
โœ… Task is automatically assigned to creator by default (Backend)
โœ… Due date validation prevents past dates (Frontend)
โœ… Task appears in project task list immediately (Frontend, Database)

4. Database Schema Visualization: VibeMap generates an interactive schema showing tables (Users, Projects, Tasks, Comments) and relationships, along with SQL suitable for PostgreSQL.

5. Component Suggestions:

  • TaskCard component

  • ProjectDashboard component

  • UserProfile component

  • NavigationBar component

  • And more...

Refining Your Project

Interactive Q&A Process: After initial generation, VibeMap asks clarifying questions:

  • "Should tasks support subtasks or dependencies?"

  • "What notification preferences do users need?"

  • "Are there specific reporting requirements?"

Smart Change Propagation: When you modify a user story, VibeMap intelligently updates related:

  • Acceptance criteria in dependent stories

  • Database schema suggestions

  • Component requirements

  • API endpoint specifications

Live Generation & Streaming

As content is generated, progress updates stream in real-time. You will see partial results accumulate for longer generations (e.g., features, user stories, acceptance criteria). This enables immediate review and faster iteration without waiting for full completion.

Understanding the Output

Kanban Board Layout

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚   Authenticationโ”‚ โ”‚ Task Management โ”‚ โ”‚  Collaboration  โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚ [User Story 1]  โ”‚ โ”‚ [User Story 5]  โ”‚ โ”‚ [User Story 9]  โ”‚
โ”‚ [User Story 2]  โ”‚ โ”‚ [User Story 6]  โ”‚ โ”‚ [User Story 10] โ”‚
โ”‚ [User Story 3]  โ”‚ โ”‚ [User Story 7]  โ”‚ โ”‚ [User Story 11] โ”‚
โ”‚ [User Story 4]  โ”‚ โ”‚ [User Story 8]  โ”‚ โ”‚ [User Story 12] โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

User Story Card Structure

๐Ÿ“‹ **User Story Title**
๐Ÿ‘ค **Role:** Team Member
โญ **Priority:** High

**Story:** As a [role], I want [goal], so that [benefit].

**Acceptance Criteria:**
โœ… AC 1: [Description] (Frontend, Backend)
โœ… AC 2: [Description] (Database)  
โœ… AC 3: [Description] (Frontend)

**Dependencies:** Links to related stories
**Estimated Effort:** 3 story points

Color-Coded Implementation Tags

  • ๐Ÿ”ต Frontend: UI/UX implementation required

  • ๐ŸŸข Backend: Server-side logic and APIs

  • ๐ŸŸก Database: Data storage and queries

  • ๐ŸŸฃ DevOps: Infrastructure and deployment

  • ๐Ÿ”ด External: Third-party integrations

Scenario Categories

  • ๐Ÿ˜Š Happy Path: Normal user flow scenarios

  • โŒ Error Scenarios: Error handling and validation

  • โš ๏ธ Edge Cases: Unusual but possible scenarios

Next Steps

Now that you've completed your first project:

  1. Explore Advanced Features: Try the database schema visualizer and component mapping

  2. Team Collaboration: Invite team members to review and refine the project

  3. Integration Setup: Export your project to tools like Jira, Linear, or Notion

  4. Continuous Refinement: Return to VibeMap as your project evolves

Pro Tips for Success

Writing Effective Descriptions

โœ… Good Description:

"A fitness tracking app where users log workouts, track progress with charts, 
set fitness goals, and share achievements with friends. Include social features 
like workout challenges and leaderboards. Integrate with popular fitness devices 
and apps like Fitbit and Apple Health."

โŒ Vague Description:

"An app for fitness stuff and social things."

Best Practices

  1. Be Specific: Include user types, key features, and integrations

  2. Mention Context: Business goals, target audience, and constraints

  3. Include Examples: Reference similar apps or specific functionality

  4. Think End-to-End: Consider the complete user journey

  5. Iterate Gradually: Start broad, then refine with AI assistance

Common Use Cases

  • ๐Ÿ›๏ธ E-commerce Platforms: Product catalogs, checkout flows, inventory management

  • ๐Ÿ“ฑ Mobile Apps: User onboarding, core features, offline capabilities

  • ๐Ÿข SaaS Products: Multi-tenant architecture, subscription billing, admin panels

  • ๐ŸŽฎ Gaming Applications: User progression, social features, monetization

  • ๐Ÿ“Š Analytics Dashboards: Data visualization, reporting, user permissions

Getting Help

If you need assistance:

  • ๐Ÿ“š Documentation: Comprehensive guides in the User Guides section

  • ๐Ÿ’ฌ In-App Chat: Click the help icon for instant AI assistance

  • ๐Ÿ“ง Support Email: support@vibemap.ai

  • ๐ŸŽฅ Video Tutorials: Available in the Help Center

  • ๐Ÿ‘ฅ Community: Join our Discord for peer support


Ready to transform your next project idea? Create your first project โ†’

VibeMap reduces project planning time by up to 80% while ensuring comprehensive coverage of requirements. Join thousands of product managers who have streamlined their planning process.

Last updated

Was this helpful?