Scaffold the .orchestra/ agent knowledge base in a project — creates folder structure, templates, README, and walks through initial roadmap setup with vision and milestones. Use when setting up a new project or adding .orchestra/ to an existing one.
Create the .orchestra/ agent knowledge base structure and set up the initial roadmap interactively.
.orchestra/
├── README.md ← Explains the folder to agents and humans
├── roadmap.md ← The score — top-level PRD (populated)
├── adr/ ← Architecture Decision Records
│ └── ADR-000-the-score.md ← Founding decision: PRDs all the way down
├── work/ ← Per-ticket work items
│ └── TEMPLATES/
│ ├── prd.md ← PRD template
│ └── spec.md ← Spec template
├── uml/ ← Mermaid diagrams (sequence, class, deployment, component, state)
└── devlog/ ← Chronological journal
└── {YYYY}-Q{N}/ ← Current quarter folder
.orchestra/ already exists — if so, STOP and report what's thereuml/)README.md — explain what .orchestra/ is, how agents should use it, and the PRD-all-the-way-down methodologyADR-000-the-score.md — document the founding decision: this project uses the orchestra methodology, PRDs are the unit of work, agents read .orchestra/ for context before actingwork/TEMPLATES/The roadmap is the score — every project needs one. Walk the user through defining it.
Ask the user:
To set up your roadmap, I need to understand the project:
1. **Project name** — What is this project called?
2. **Vision** — In 1-2 sentences, what does "done" look like at the highest level?
(Example: "A chiropractic app that replaces paper SOAP notes with AI-assisted documentation")
3. **Who is the audience?** — Who benefits when this is done?
Wait for answers before proceeding.
Ask the user:
Now let's break the vision into milestones. A milestone is a meaningful checkpoint —
something you could demo, ship, or celebrate.
What are your first 2-4 milestones? For each one:
- **Name** — short, memorable (e.g., "MVP Launch", "Beta Testing", "API Integration")
- **Objective** — what does "done" look like for this milestone?
Don't overthink it — milestones can be added and refined later.
What matters is having a starting score to play from.
If the user is unsure, help them derive milestones from the vision:
Create .orchestra/roadmap.md as a PRD:
# {Project Name} Roadmap
**Objective:** {Vision — 1-2 sentences}
## Success Criteria
- [ ] {Derived from vision — what "fully done" looks like}
- [ ] {Second criterion}
- [ ] {Third criterion}
## Context
{Why this project matters. Who it serves. What problem it solves.}
## Milestones
| Material | Location | Status |
|----------|----------|--------|
| {Milestone 1 name} | .orchestra/work/{slug}/prd.md | Not Started |
| {Milestone 2 name} | .orchestra/work/{slug}/prd.md | Not Started |
| {Milestone 3 name} | .orchestra/work/{slug}/prd.md | Not Started |
## References
- ADR-000: [The Score](.orchestra/adr/ADR-000-the-score.md)
For each milestone, create a stub PRD at .orchestra/work/{slug}/prd.md:
---