What problem does it solve?
It solves the fragmentation of the software development process by unifying idea, discussion, spec, implementation, review, and merge into a single memory-first orchestration stream across parallel lanes.
Core Features & Use Cases
- Lead×Wing development orchestration: Use lead to hear, debate, and decide, then hand off work to wing lanes for implementation and reporting.
- Wire-based stateful communication: Transport decisions and progress as thread messages with explicit kinds (task/question/approve/complete) to derive control state.
- Memory-first decision lineage: Persist decisions and rationale in canonical spec memory, then project it into future session contexts.
- Parallel wing tracking with HITL escalation: Automatically self-run when specs are clear, and switch to human-in-the-loop when design decisions or ambiguity require lead control.
- Multi-phase dev flow: Run a structured 6-phase loop (hearing → council discussion → spec memory → wing handoff → parallel tracking → merge + feedback).
Quick Start
Ask your AI to set up a dev-flow run by creating a wing lane, sending a task spec via wire, and then tracking control state until the wing reports complete and you proceed to merge.