mission-orchestrator

# Mission Orchestrator ## Overview Wraps the entire attune development lifecycle (brainstorm → specify → plan → execute) into a single mission with automatic state detection, type selection, and phase routing. Follows the "persistent presence lens" pattern from `spec-kit:speckit-orchestrator`: delegates entirely to existing skills via `Skill()` calls, never re-implements phase logic. ## When To Use - Starting a new project from scratch (full lifecycle) - Resuming an interrupted project workflow - Running a focused tactical implementation from existing specs - Quick-fixing from an existing implementation plan ## When NOT To Use - Running a single phase directly (use `/attune:brainstorm`, `/attune:specify`, etc.) - Non-project work (code review, debugging, research) - When you need fine-grained control over phase transitions ## Mission Lifecycle ``` 1. State Detection Scan for existing artifacts (project-brief.md, specification.md, etc.) | 2. Mission Type Selection Auto-detect type based on artifacts, or accept user override | 3. Phase Routing Loop For each phase in the mission type: a. Pre-phase validation (check prerequisites) b. Invoke Skill(attune:{phase-skill}) c. Post-phase artifact check (verify output exists) d. Post-phase backlog triage (create GitHub issues for out-of-scope items after brainstorm/specify) e. Update mission state f. User checkpoint (skippable with --auto) g. Error...