seed
Unified project seeding — from idea capture to build-ready.
Synopsis
Description
The seed command manages the full project initialization workflow: creating context documents, merging them into a unified specification, and auto-generating all AI context files and planning scaffolds needed for the build loop.
Pipeline
bootspring go ← One command does everything below
│
bootspring seed init → edit docs → bootspring seed go → bootspring build next
↓ ↓ ↓
.bootspring/context/ SEED.md + CLAUDE.md + Build initialized,
(templates) AGENTS.md + CODEX.md + first task ready
GEMINI.md + planning/
+ BUILD_STATE.json
Commands
init
Create context document templates in .bootspring/context/.
Options:
| Option | Description |
|---|---|
--preset=<preset> | Document preset (essential, startup, full, technical, investor) |
--force | Overwrite existing templates |
Presets:
| Preset | Documents | Use Case |
|---|---|---|
essential | 4 | Quick start (vision, audience, business-model, prd) |
startup | 7 | Default — full startup context |
full | 8 | All document types |
technical | 4 | Dev-focused (vision, prd, technical-spec, roadmap) |
investor | 6 | Fundraising context |
Creates:
.bootspring/context/
├── README.md # Workflow guide
├── VISION.md # Problem, solution, core values
├── AUDIENCE.md # Target audience, personas, ICP
├── BUSINESS_MODEL.md # Revenue, pricing, unit economics
├── PRD.md # Product requirements, user stories
├── TECHNICAL_SPEC.md # Architecture, tech stack
├── ROADMAP.md # Phases, milestones
├── MARKET.md # TAM/SAM/SOM (startup/full presets)
└── COMPETITORS.md # Competitive landscape (full preset)
Example:
go
Complete workflow in one command — detect + init + merge + generate + build init.
Options:
| Option | Description |
|---|---|
--preset=<preset> | Document preset (essential, startup, full, technical) |
--force | Overwrite existing files |
--edit-first | Stop after templates for manual editing |
Runs 5 steps automatically:
- Detect — scans
package.jsonfor stack and features - Seed — creates context templates in
.bootspring/context/ - Merge — combines into
SEED.md - Generate — creates AI context files +
planning/ - Build init — initializes build state from
planning/TODO.md
After completion, edit planning/TODO.md with real tasks, then run bootspring build next.
There is also a top-level alias: bootspring go (identical behavior).
from-codebase
Auto-detect tech stack from existing code and generate context.
Alias: from-code, detect
Reads package.json and git history to identify your stack, then generates context templates with the technical preset.
merge
Merge context docs into SEED.md and auto-generate all project files.
Options:
| Option | Description |
|---|---|
--output=<path> | Custom output path (default: SEED.md) |
--force | Overwrite existing files |
This is the key command that bridges context documents to the build loop. It:
- Reads all
.mdfiles from.bootspring/context/ - Sorts them in canonical order
- Merges into
SEED.md - Auto-generates all AI context and planning files
Files generated:
| File | Purpose |
|---|---|
SEED.md | Merged project specification |
CLAUDE.md | AI context for Claude Code / Cursor |
AGENTS.md | Agent context (Linux Foundation AAIF standard) |
CODEX.md | OpenAI Codex / ChatGPT context |
GEMINI.md | Google Gemini CLI context |
planning/TODO.md | Build task checklist (source of truth) |
planning/MASTER_PLAN.md | Vision and phases |
planning/CONTEXT.md | Condensed build context |
planning/AGENTS.md | Planning-specific agent instructions |
Example:
status
Show context documents and SEED.md readiness.
Shows which context documents exist, their size (draft vs ready), and whether SEED.md has been created.
generate
Generate/regenerate document templates in .bootspring/context/.
| Option | Description |
|---|---|
--preset=<preset> | Document preset |
--force | Overwrite existing templates |
doc
View a specific context document.
Accepts document name with fuzzy matching: vision, prd, roadmap, etc.
export
Export context documents as JSON.
build
Bridge to the build loop — check readiness.
Checks for SEED.md and all required context/planning files. Shows clear status and next steps.
Complete Workflow
Fastest Path (One Command)
Both detect your stack, create templates, merge into SEED.md, generate all AI context files, and initialize the build. Then:
Step-by-Step (New Project)
Existing Codebase
Just Agent Files (No Seed)
Related Commands
bootspring generate— Generate agent files + planning scaffoldbootspring build— Build loop task managementbootspring quality— Quality gates and checks
Related Guides
- Seed Generator Workflow — Dashboard-based generation
- BYOK Seed Generator — Bring Your Own Key generation