Multi-sprint orchestration and dependency tracking.
12 sprints running. One command to see them all. Orchard coordinates parallel research across teams with dependency graphs, conflict detection, and unified dashboards.
npm install -g @grainulation/orchardOr use directly:
npx @grainulation/orchard statusCreate orchard.json in your project root:
{
"sprints": [
{
"path": "./sprints/auth-scaling",
"question": "How should we scale auth for 10x traffic?",
"depends_on": [],
"assigned_to": "alice",
"deadline": "2026-03-20",
"status": "active"
},
{
"path": "./sprints/data-migration",
"question": "What's the safest migration path for the user table?",
"depends_on": ["./sprints/auth-scaling"],
"assigned_to": "bob",
"deadline": "2026-03-25",
"status": "active"
}
]
}Then:
orchard plan # Show the dependency graph
orchard status # Check status of all sprints
orchard sync # Sync status from sprint directories
orchard dashboard # Generate unified HTML dashboard- Sprint dependency graphs -- "sprint B needs sprint A's results first"
- Cross-sprint conflict detection -- when two sprints reach opposing conclusions
- Team assignment -- who's running which sprint
- Unified status dashboard across all active sprints
- Sprint scheduling and deadline tracking
- Topological sort -- determines execution order, flags cycles
| Command | Description |
|---|---|
orchard plan | Show sprint dependency graph |
orchard status | Show status of all tracked sprints |
orchard assign <path> <person> | Assign a person to a sprint |
orchard sync | Sync sprint states from directories |
orchard dashboard [outfile] | Generate unified HTML dashboard |
orchard init | Initialize orchard.json |
orchard serve | Start the portfolio dashboard web server |
Orchard flags two types of cross-sprint conflicts:
- Opposing recommendations -- two sprints make recommendations on the same topic that contradict
- Constraint-recommendation tension -- one sprint's constraints conflict with another's recommendations
Depends only on @grainulation/barn (internal ecosystem utilities); no third-party runtime deps. Node built-ins otherwise.
| Tool | Role |
|---|---|
| wheat | Research engine -- grow structured evidence |
| farmer | Permission dashboard -- approve AI actions in real time |
| barn | Shared tools -- templates, validators, sprint detection |
| mill | Format conversion -- export to PDF, CSV, slides, 26 formats |
| silo | Knowledge storage -- reusable claim libraries and packs |
| harvest | Analytics -- cross-sprint patterns and prediction scoring |
| orchard | Orchestration -- multi-sprint coordination and dependencies |
| grainulation | Unified CLI -- single entry point to the ecosystem |
See CHANGELOG.md for release history.
MIT