spec-kitty.plan

# /spec-kitty.plan - Create Implementation Plan **Version**: 0.11.0+ ## 📍 WORKING DIRECTORY: Stay in the repository root checkout **IMPORTANT**: Plan works in the repository root checkout. NO worktrees created. ```bash # Run from project root (same directory as /spec-kitty.specify): # You should already be here if you just ran /spec-kitty.specify # Creates: # - kitty-specs/<mission_slug>/plan.md → In repository root checkout # (the NNN- prefix in the directory listing is display-only metadata) # - Commits to target branch # - NO worktrees created ``` **Do NOT cd anywhere**. Stay in the repository root checkout. ## Mission Handle Rule `/spec-kitty.plan` operates on an existing mission, so use `--mission <handle>` when the CLI needs a mission selector. - `<handle>` can be the mission's `mission_id` (ULID), `mid8` (first 8 chars of the ULID), or `mission_slug`. - Prefer `mission_id` or `mid8` when the repo has multiple similarly named missions. - The resolver disambiguates by `mission_id` and returns a structured `MISSION_AMBIGUOUS_SELECTOR` error on ambiguity — there is no silent fallback. ## User Input The content of the user's message that invoked this skill (everything after the skill invocation token, e.g. after `/spec-kitty.<command>` or `$spec-kitty.<command>`) is the User Input referenced elsewhere in these instructions. You **MUST** consider this user input before proceeding (if not empty). ## Commit Boundary (issue #846) `/spec-kitty.plan` will r...