spec-kitty.specify

# /spec-kitty.specify - Create Mission Specification **Version**: 0.11.0+ ## 📍 WORKING DIRECTORY: Stay in the repository root checkout **IMPORTANT**: Specify works in the repository root checkout. NO worktrees are created. ```bash # Run from the repository root checkout: cd /path/to/project/root # Your repository root checkout # All planning artifacts are created in the project root and committed: # - kitty-specs/<mission_slug>/spec.md → Created in project root # (use the mission_slug returned by `mission create`; the numeric NNN- prefix # is display-only and is assigned at merge time) # - Committed to target branch (from create JSON: target_branch/base_branch) # - NO worktrees created ``` **Worktrees are created later** during `/spec-kitty.implement`, after task finalization computes execution lanes. ## Mission Handle Rule Before `mission create`, there is no mission handle yet. - Do **not** pass `--mission` to `spec-kitty agent mission branch-context`. - Do **not** pass `--mission` to `spec-kitty agent mission create`. - After `create` succeeds, use `--mission <handle>` for commands that operate on the created mission. - `<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 (every...