Documentation
Feature Guide

Work Breakdown Structure (WBS) Creation

Generate a complete project structure with tasks, epics, features, and dependencies using AI. Choose between uploading a document or answering guided questions to create your Work Breakdown Structure automatically.

Two Ways to Create Your WBS

Method 1: Document Upload

Upload an existing project document (PDF, TXT, or Markdown) and let AI extract the structure automatically.

  • Best for: Existing project documentation
  • Supports: PDF, TXT, Markdown files
  • Total cost: ~35 credits

Method 2: AI Interview

Answer a few guided questions about your project, and AI will generate a structured document for WBS creation.

  • Best for: New projects or brainstorming
  • Interactive: Step-by-step questionnaire
  • Total cost: ~45 credits

Method 1: Document Upload

Step-by-Step Guide

1

Prepare your document

Create or gather a project document in PDF, TXT, or Markdown format. Include project phases, tasks, milestones, and any dependencies. Maximum file size is 10MB.

2

Open the upload dialog

Click the "Upload Document" button in the top-right corner of your project canvas. Select the "Upload Document" tab.

3

Upload your file

Drag and drop your file or click to browse. The file will be uploaded to Supabase Storage and processing will begin automatically.

4

Wait for processing

The document will be processed: text extracted, chunked, and embedded. This typically takes 10-30 seconds depending on file size. You'll see a "Processing..." status.

5

Generate WBS

Once processing is complete (status shows "Ready"), click "Generate WBS" to create your project structure. AI will analyze the document and create nodes with dependencies.

6

Review and refine

The generated nodes will appear on your canvas. Review them, adjust positions, and add any missing tasks manually. You can regenerate if needed.

Supported File Types

PDF Files

Best for: Project proposals, requirements documents, technical specifications. Text is extracted using OCR.

Text Files (.txt)

Best for: Simple project descriptions, plain text notes. Fastest processing time.

Markdown (.md)

Best for: Structured documentation, README files, formatted project plans.

Tips for Better Results

  • Include clear section headings (e.g., "Phase 1", "Tasks", "Dependencies")
  • Mention time estimates or deadlines when available
  • List dependencies explicitly (e.g., "Task B depends on Task A")
  • Keep documents under 100 pages for optimal processing
  • Use consistent formatting and structure

Method 2: AI Interview

The AI Interview guides you through a structured questionnaire to capture all essential project information. Your answers are used to generate a comprehensive project document that is then processed into a WBS.

Interview Steps

Step 1

Project Basics

Enter project name, owner, goal, and hard deadline. This provides context for the entire project.

Fields: Project name, Owner name and role, Executive summary/goal, Hard deadline date
Step 2

Phases & Scope

Define major project phases with time estimates. Add dependencies between phases and any constraints.

Fields: Phase names and descriptions, Best case / Worst case estimates (days), Dependencies between phases, Constraints or blockers
Step 3

Milestones

Set key checkpoints and target dates. Milestones help track progress and identify critical dates.

Fields: Milestone names, Target dates or week numbers, Optional descriptions
Step 4

Risk Register

Identify potential risks with likelihood and impact. This helps the AI understand project uncertainties.

Fields: Risk titles and descriptions, Likelihood (Low/Medium/High), Impact in days if risk occurs, Mitigation strategies

Document Preview & Approval

5

Review generated document

After completing the interview, AI generates a structured markdown document. Review it in the preview dialog.

6

Edit if needed

Click "Edit" to make changes to the generated document. You can modify any section before approval.

7

Regenerate (optional)

If you're not satisfied, click "Regenerate" to create a new version. This costs additional credits.

8

Approve & Generate WBS

Once satisfied, click "Approve & Generate WBS" to save the document and create your project structure.

Credit Costs

Method 1: Document Upload

Document Upload5 credits
Document Processing10 credits
WBS Generation20 credits
Total35 credits

Method 2: AI Interview

Document Generation15 credits
Document Processing10 credits
WBS Generation20 credits
Total45 credits
* Regenerating document costs an additional 15 credits

Credit Balance

Make sure you have enough credits before starting. You can check your balance in the upload dialog or purchase more credits from your account page.

Understanding Your Generated WBS

Node Types

Epic

High-level project themes or major deliverables

Feature

Significant functionality or capability

User Story

User-facing requirements or use cases

Task

Specific work items that can be assigned and tracked

Milestone

Key checkpoints or deadlines

Risk

Potential issues or uncertainties

Dependencies

AI automatically creates dependency connections between nodes based on the document content. Connections are visualized as lines between nodes, with smart positioning (e.g., bottom of feature to top of user story).

// Example dependency structure
Epic → Feature → User Story → Task
Dependencies flow from parent to child nodes

Tips & Best Practices

Be specific in documents

Include concrete details about tasks, phases, and dependencies. Vague descriptions lead to generic WBS structures.

Use consistent terminology

Stick to the same naming conventions throughout your document. This helps AI identify relationships correctly.

Include time estimates

Mention durations, deadlines, or milestones. This information helps create more accurate project structures.

Review before approval

Always review the generated document or WBS before finalizing. Make edits if needed to ensure accuracy.

Start with phases

In the interview, begin with high-level phases before diving into detailed tasks. This creates better hierarchy.

Document dependencies explicitly

Clearly state which tasks depend on others. Use phrases like "depends on", "requires", or "must complete first".

Refine after generation

The generated WBS is a starting point. Manually add missing tasks, adjust dependencies, and reorganize as needed.

Use milestones strategically

Include key checkpoints and deadlines. They help track progress and identify critical path items.