Complete Task

Overview

Commit changes, push to remote, create pull request, and transition issue to "Code Review" status.

{TASK_KEY}: Story/Issue ID from the issue tracker (e.g., FB-6, PROJ-123, KAN-42)
Branch Name Format: Use short format {type}/{TASK_KEY} (e.g., feat/FB-6, fix/PROJ-123)
- Short format is recommended: feat/FB-6 (not feat/FB-6-file-watching-workspace-commands)
- Important: Be consistent within a project - use the same format for all branches
Spec Summary: Content from spec file located at specs/{FEATURE_DOMAIN}/spec.md
- Contains Blueprint (Context, Architecture, Anti-Patterns) and Contract (DoD, Guardrails, Scenarios)
- Used in PR body to document feature contracts
Plan Summary: Content from plan file located at .plans/{TASK_KEY}-*.plan.md
- Plan File Selection: If multiple files match the pattern .plans/{TASK_KEY}-*.plan.md:
  - Use the most recently modified file (check file modification time)
  - If modification time cannot be determined, use the first file found alphabetically
  - Report which file was selected: "Using plan file: {filename}"