Mission Run Overview
Mission Run: Local Custom Mission Loader
Let teams author and run their own local mission definitions as first-class peers to built-in missions through the existing runtime and composition pipeline.
Phase 6 issue #505 closes the gap that today only built-in missions (software-dev, research, documentation, plan) can drive Spec Kitty workflows. This v1 tranche adds a local custom mission loader so a project can keep its own .kittify/missions/<key>/ YAML definitions and run them through the same internal runtime, StepContractExecutor, and ProfileInvocationExecutor pipeline as built-ins. Distribution stays local — SaaS registry, mission install, and cross-team sharing remain deferred under #516. Retrospective execution, retrospective.yaml, synthesizer handoff, and HiC/autonomous gating stay out of scope per #506-#511.