story-to-plan-orchestratorlisted

# Story-To-Plan Orchestrator Coordinate the path from product intent to an evidence-backed implementation plan. Let each component skill own its artifact; this skill owns routing, invalidation, resumption, and packet assembly. This is a process overlay and multi-stage entry point. The component skills remain independently usable. For a review-only request, assess packet coherence and readiness and return findings without rebuilding artifacts. Resume or repair stages when requested. Return artifacts in the conversation unless file output was requested; pipeline preparation does not authorize product implementation or external publication. ## When To Use - produce a complete Story Card, Repo Context, and Implementation Plan handoff - run or repair two or more preparation stages - select and materialize one slice from a Split Story Set before scouting - resume or validate a partial packet whose next valid stage is unclear - reconcile stale or contradictory stage outputs before coding ## Not For - one requested artifact; use its owning component skill - direct code implementation after preparation - broad product strategy, architecture review, test strategy, or security review ## Ownership | Owner | Artifact | Decisions it owns | |---|---|---| | `story-clarifier` | Story Card or Split Story Set | behavior, scope, acceptance, and story readiness | | `story-repo-scout` | Repo Context | repository evidence, proposed-path basis, and repo-context readiness | | `story-implemen