mission-orchestrator

## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Mission Lifecycle](#mission-lifecycle) - [Interactive Plan Review](#interactive-plan-review) - [Mission Types](#mission-types) - [Phase-to-Skill Mapping](#phase-to-skill-mapping) - [Session Recovery](#session-recovery) - [Module Reference](#module-reference) - [Related Skills](#related-skills) - [Related Commands](#related-commands) - [Exit Criteria](#exit-criteria) # 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 use...