Merge Context Documents

Note: The seed synthesize command has been replaced by seed merge. If you're looking for the old synthesize docs, see the updated workflow below.

The seed merge command reads your context documents and creates a unified SEED.md, then auto-generates all agent files and planning documents.

Command#

What It Does#

1. Reads Context Documents#

The command reads all documents from .bootspring/context/:

• VISION.md - Problem, solution, unique value
• AUDIENCE.md - Target users, personas
• BUSINESS_MODEL.md - Revenue, pricing
• PRD.md - Product requirements
• TECHNICAL_SPEC.md - Architecture, tech stack
• ROADMAP.md - Development phases
• MARKET.md - TAM/SAM/SOM (with startup/full presets)
• COMPETITORS.md - Competitive landscape (with full preset)

2. Generates SEED.md#

Creates a unified specification containing:

• Project overview
• Tech stack configuration
• MVP features
• Development standards

3. Auto-Generates Project Files#

After creating SEED.md, merge automatically runs generate to create:

Example Usage#

Basic Merge#

With Force Overwrite#

Overwrites all existing files without prompting.

Enrichment Workflow (Existing Codebases)#

If your context docs came from seed from-codebase and still need business/context enrichment:

After Merge#

Review SEED.md#

Make Adjustments#

Edit SEED.md to:

• Adjust tech stack choices
• Reorder MVP features
• Add missing details
• Correct any inaccuracies

Start Building#

Troubleshooting#

"No context documents found"#

Make sure you have documents in .bootspring/context/:

If empty, run seed init first:

"Incomplete context documents"#

Merge works best with complete documents. At minimum:

• VISION.md
• PRD.md

Run seed init to create templates, then edit them:

"SEED.md already exists"#

Use --force to overwrite:

Or rename the existing file:

Best Practices#

Complete Context Docs First#

Better context documents = better SEED.md:

Review Before Building#

Always review SEED.md before starting the build loop:

• Verify tech stack is correct
• Check MVP feature priorities
• Ensure user stories are accurate

Keep SEED.md Updated#

SEED.md is a living document. Update it as your project evolves:

---

Related#

• Seed Overview - Full seed workflow
• Scaffold Presets - Framework options
• CLI Seed Reference - Full command reference