spec-kitty.research

**Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `kitty-specs/<feature>/tasks/`). Never refer to a folder by name alone. **In repos with multiple missions, always pass `--mission <handle>` to every spec-kitty command.** The `<handle>` can be the mission's `mission_id` (ULID), `mid8` (first 8 chars of the ULID), or `mission_slug`. 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). ## Location Pre-flight Check **BEFORE PROCEEDING:** Verify you are working in the repository root checkout. ```bash pwd git branch --show-current ``` **Expected output:** - `pwd`: Should end with your project root directory path - Branch: Should show your mission branch (e.g. `kitty/mission-<slug>-<mid8>` or a legacy `NNN-feature-name` form), NOT `main` **If you see the main branch or the wrong directory path:** ⛔ **STOP - You are in the wrong location!** This command creates research artifacts in your feature directory. You must be in the repository root checkout. **Correct the issue:*...