Phase 2: Document Generation
Duration: Automatic (1-2 seconds)
Your answers are transformed into comprehensive, professional documents.
Overview#
After completing the Idea Capture wizard, Bootspring automatically generates all documents based on your selected preset. Each document is structured, formatted, and ready for review or sharing.
How It Works#
┌─────────────────────┐
│ PRESEED_CONFIG.json │
│ (Your Answers) │
└──────────┬──────────┘
│
┌──────────▼──────────┐
│ Template Engine │
└──────────┬──────────┘
│
┌──────────────────────┼──────────────────────┐
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
VISION.md AUDIENCE.md MARKET.md PRD.md ROADMAP.md
Generated Files#
All documents are created in .bootspring/preseed/:
.bootspring/
└── preseed/
├── PRESEED_CONFIG.json # Source of truth (editable)
├── VISION.md # Problem/solution foundation
├── AUDIENCE.md # Target audience and personas
├── MARKET.md # Market sizing and trends
├── COMPETITORS.md # Competitive landscape
├── BUSINESS_MODEL.md # Revenue model and pricing
├── PRD.md # Product requirements
├── TECHNICAL_SPEC.md # Architecture decisions
└── ROADMAP.md # Development timeline
Document Details#
VISION.md#
The foundation document that explains why your product exists.
Contains:
- Problem statement with pain points
- Solution overview
- Key features
- Unique value proposition
- Why now timing
Example Output:
AUDIENCE.md#
Detailed breakdown of who you're building for.
Contains:
- Primary audience definition
- Market segments
- Detailed personas (2-4)
- Ideal Customer Profile (ICP)
- Anti-personas (who you're not building for)
Example Structure:
MARKET.md#
Market sizing and opportunity analysis.
Contains:
- TAM/SAM/SOM calculations
- Market trends
- Growth projections
- Timing factors
COMPETITORS.md#
Competitive landscape analysis.
Contains:
- Direct competitor profiles
- Indirect competitors
- Feature comparison matrix
- Positioning strategy
- Competitive advantages
BUSINESS_MODEL.md#
Revenue and pricing strategy.
Contains:
- Revenue model selection
- Revenue streams breakdown
- Pricing tiers with features
- Unit economics targets
- Financial projections
PRD.md#
Product requirements document.
Contains:
- Product vision statement
- MVP feature list with priorities
- User stories with acceptance criteria
- Success metrics
- Out of scope items
- Dependencies and assumptions
Example Structure:
TECHNICAL_SPEC.md#
Architecture and technical decisions.
Contains:
- Tech stack selection with rationale
- System architecture overview
- Database schema outline
- API design principles
- Integration requirements
- Security considerations
ROADMAP.md#
Development timeline and milestones.
Contains:
- Phase breakdown with features
- Timeline estimates
- Key milestones
- Dependencies between phases
- Resource requirements
Regenerating Documents#
Documents can be regenerated anytime:
Regeneration:
- Reads the latest
PRESEED_CONFIG.json - Applies the document template
- Overwrites existing files
- Preserves formatting
Document Format#
All generated documents follow consistent formatting:
- Markdown format for universal compatibility
- Structured headings (H1, H2, H3 hierarchy)
- Tables for data comparison
- Code blocks for examples
- Bullet lists for enumeration
- Git-friendly line lengths and formatting
Customization#
While documents are generated from templates, you can:
Edit the Config#
Edit Documents Directly#
Documents can be edited directly, but edits will be lost on regeneration. For persistent changes, update the config instead.
Add Custom Sections#
After generation, you can add sections to documents. Mark them clearly so you know what to preserve:
Export Configuration#
Export your preseed configuration for backup or sharing:
What Happens Next#
After document generation:
- Review all documents - Read through each generated file
- Identify gaps - Note anything missing or incorrect
- Move to Phase 3 - Refinement to improve documents