shipkit-plan

# shipkit-plan - Implementation Planning with Failure Mode Prevention **Purpose**: Transform feature specifications into validated implementation plans that prevent common planning failures: orphaned foundations, magical steps, codebase blindness, and incomplete coverage. --- ## When to Invoke **User triggers**: - "Plan how to build this" - "Create implementation plan" - "How should we implement this feature?" - "Design the technical approach" **After**: - `/shipkit-spec` has created specification for the feature - Feature is ready for implementation planning --- ## Prerequisites **Check before starting**: - Spec exists: `.shipkit/specs/todo/[feature-name].json` or `.shipkit/specs/active/[feature-name].json` - Stack defined: `.shipkit/stack.json` (from shipkit-project-context) **UI-Heavy Feature Check**: - If spec describes significant UI/UX, check if architecture.json has UI patterns or stack.json has a frontend framework - If neither exists, warn: "This feature has significant UI — consider running `/shipkit-engineering-definition` first to define UI patterns" - Do NOT block on prototyping — proceed with planning **Optional but helpful**: - Architecture decisions: `.shipkit/architecture.json` - Data contracts: `.shipkit/engineering-definition.json` (see `components[].dataContracts`) --- ## Arguments If `$ARGUMENTS` is provided (e.g. `/shipkit-plan recipe-sharing`), use it as the spec name. Try to read `.shipkit/specs/todo/$ARGUMENTS.json` or `.shipkit/specs/act...