Validating

If .khuym/onboarding.json is missing or stale for the current repo, stop and invoke khuym:using-khuym before continuing.

Validating is the hard gate between planning and execution. It rejects beautiful fantasy plans by requiring repo/system evidence, feasibility proof, and current-story readiness.

Required Inputs

• history/<feature>/CONTEXT.md
• history/<feature>/discovery.md
• history/<feature>/approach.md
• approved shape artifact: direct note, spike question, small plan, phase-plan.md, or epic-map.md
• mode-required current-work artifacts: current-story-pack.md, phase-<n>-contract.md, or story map
• .beads/ for the current execution surface when beads are required

If any mode-required input is missing, return to khuym:planning. If the shape artifact has not been approved by the user, stop immediately.

Operating Contract