What problem does it solve? Teams need a structured way to decide what a sprint takes on before any code is written. This Skill runs an interactive planning ceremony with the project owner that reconciles the project's durable corpora with reality, drafts final-form artifact deltas and work items, resolves open issues, and terminates at an approved sprint with a fixed completion contract. ## Core Features & Use Cases - Estate-aware planning: Detects which skill families (ok-planner, ok-plumbline, ok-workspaces) are present via filesystem checks and loads each family's ceremony contribution, so one canonical verb covers any project configuration. - Eight-phase spine: Runs Layout, Frame, Reconcile, Dialogue, Draft, Resolve, Sign-off, and Terminal phases in order, following each present family's contribution under every phase heading. - Fixed completion contract: Produces a sprint document with corpus deltas and flat work items stated well enough to be picked up cold, plus a handoff line that starts execution under the native goal mechanism. - Use Case: A project owner runs /plan-sprint at the start of a cycle; the session pulls in ruled issues, reconciles work done out of band, drafts the sprint, and ends with an owner-approved document ready for separate execution. ## Quick Start Run the /plan-sprint slash command in a project containing a .ok-planner estate to start an interactive sprint planning session with the owner.
