spec-kitty.implement

# /spec-kitty.implement - Execute Work Package Implementation **Version**: 0.12.0+ ## Purpose Execute the implementation of a work package according to its prompt file. Follow TDD practices, respect file ownership boundaries, and apply safety guardrails for bulk operations. --- ## Working Directory **IMPORTANT**: This step works inside the execution workspace (worktree) allocated by `spec-kitty agent action implement WPxx --agent <name>`. Do NOT modify files outside your `owned_files` boundaries. **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). ## Governance Payload Contract The prompt produced by `spec-kitty agent action implement` is guaranteed to carry the following surfaces. Trust the prompt; do not consult external governance sources unless explicitly cited by a fetch command + when-doing rule in the prompt. **Guaranteed bodies** (verbatim in the...