Workflow Approval
Professional document review and approval workflow for preseed documents.
The workflow approval system provides a structured process for reviewing, refining, and approving your preseed documents before moving to the seed phase.
Overview#
Instead of generating all documents at once and hoping they're right, the workflow system guides you through:
- Generate each document type
- Review the content
- Refine as needed
- Approve or reject
- Move to next document
This ensures quality and completeness before you start building.
Starting a Workflow#
This initializes the workflow state and begins the approval process.
Workflow Commands#
workflow start#
Begin a new workflow from the beginning.
What happens:
- Workflow state is initialized
- You're guided to the first document
- Progress tracking begins
workflow resume#
Continue from where you left off.
Picks up at the last incomplete step.
workflow status#
View current progress.
Example output:
Overall Progress: [████████░░░░░░░░░░░░░░░░] 25%
4/16 documents approved
Phases:
✓ Foundation (2/2)
✓ Vision
✓ Audience
▶ Market Analysis (0/2) ← current
◇ Market
○ Competitors
○ Business Strategy (0/2)
○ Business Model
○ PRD
○ Technical Planning (0/2)
○ Technical Spec
○ Roadmap
Status indicators:
✓- Approved◎- In review◇- Draft (generated, not reviewed)✗- Rejected (needs revision)○- Pending (not yet generated)
workflow reset#
Start over from scratch.
This clears all workflow state but keeps your documents.
Document Commands#
Manage individual documents within the workflow.
Approve a Document#
Marks the document as approved and moves to the next step.
Reject a Document#
Marks for revision with feedback. The feedback is saved for reference.
Edit a Document#
Opens the document in your default editor ($EDITOR or vim).
View a Document#
Displays the document content in the terminal.
Submit for Review#
Calculates a quality score and flags potential issues.
Document Types#
| Type | File | Description |
|---|---|---|
vision | VISION.md | Problem, solution, unique value |
audience | AUDIENCE.md | Target users, personas, ICP |
market | MARKET.md | TAM/SAM/SOM, trends |
competitors | COMPETITORS.md | Competitive analysis |
business-model | BUSINESS_MODEL.md | Revenue, pricing |
prd | PRD.md | Product requirements |
technical-spec | TECHNICAL_SPEC.md | Architecture, stack |
roadmap | ROADMAP.md | Phases, milestones |
Workflow Phases#
Documents are organized into phases:
Phase 1: Foundation#
- Vision
- Audience
Start here. These documents inform everything else.
Phase 2: Market Analysis#
- Market
- Competitors
Understand your space.
Phase 3: Business Strategy#
- Business Model
- PRD
Define how you'll make money and what you'll build.
Phase 4: Technical Planning#
- Technical Spec
- Roadmap
Plan the implementation.
Quality Scoring#
When you submit a document for review, Bootspring calculates a quality score:
Output:
Quality Analysis: VISION.md
Score: 78/100
Strengths:
✓ Clear problem statement
✓ Specific solution defined
✓ Unique value proposition present
Areas for improvement:
⚠ Pain points could be more specific
⚠ Missing "Why now?" section
⚠ No supporting data/metrics
Suggestions:
1. Add 2-3 specific pain points with examples
2. Include market timing rationale
3. Add industry statistics or research citations
Example Workflow#
Step 1: Start the Workflow#
Step 2: Generate First Document#
The workflow prompts you to generate the Vision document:
Step 3: Review#
Score: 72/100 - "Good, but could be better"
Step 4: Edit#
Make improvements based on feedback.
Step 5: Re-review#
Score: 89/100 - "Excellent"
Step 6: Approve#
Workflow moves to next document (Audience).
Step 7: Continue#
Repeat for each document until all are approved.
Step 8: Complete#
Overall Progress: [████████████████████████████████] 100%
8/8 documents approved
All documents approved! Ready for seed phase.
Next steps:
bootspring seed synthesize
Team Workflows#
For teams, combine workflow with cloud sync:
Assign Documents#
Review Process#
Tips#
Don't Rush#
The workflow is designed to slow you down for a reason. Spending time here saves time later.
Use the Quality Score#
Aim for 80+ on important documents like Vision and PRD.
Iterate#
It's normal to reject and revise documents multiple times. That's the point.
Get Feedback#
Share documents with others before approving:
Related#
- preseed start - Smart entry point
- Cloud Sync - Team collaboration
- seed synthesize - Next step after workflow