story-implementation-orchestratorlisted

# Story Implementation Orchestrator Coordinate the story-to-plan workflow without duplicating the detailed instructions from the component skills. This is a companion process overlay. Pair it with the component story skills when the user wants end-to-end preparation before implementation. ## When To Use - run the full pipeline from rough idea to actionable implementation plan - prepare a story for a coding agent or human before code changes start - choose which story-prep stages can be skipped because their outputs already exist - produce a single handoff containing story, repo context, and implementation plan ## Not For - direct implementation after a plan already exists - story clarification only; use `user-story-clarifier` - repo scouting only; use `story-repo-scout` - model-aware planning only; use `story-implementation-planner` - security review, broad architecture review, or whole-repo analysis ## Pipeline 0. **Inspect input.** Classify which stages already exist in the input (single story card? split story set? Repo Context? Implementation Plan?). Run the matching readiness check on each. Run only the missing or failing stages. This is the orchestrator's main reason to exist: do not re-run a stage whose output already passes its readiness check. 1. **Clarify.** Use `user-story-clarifier` unless the single-story or split-set readiness check passes. 2. **Select slice.** If clarification returns a split story set, plan only the first shippable sl