pr

Create a pull request based on issue #$ARGUMENTS. Follow these steps systematically:

Phase 0: Setup and Worktree Decision

1. Ask the user: "Do you want to use a git worktree for this issue? (y/n)"
   • If yes: Create worktree ./worktree-issue-$ARGUMENTS-[desc] with branch issue-$ARGUMENTS-[desc]
   • If no: Create a new branch: git checkout -b issue-$ARGUMENTS-[brief-description]

Phase 1: Issue Analysis and Complexity Assessment

2. Analyse the issue:

   • Launch a haiku agent to: fetch issue #$ARGUMENTS with gh issue view, summarise it, identify related code areas using Glob/Grep, and return structured findings

3. Assess complexity (SIMPLE / MEDIUM / COMPLEX):

   • SIMPLE: Single file, typos, docs-only, trivial test updates
   • MEDIUM: 2-5 files, bug fixes, standard test updates
   • COMPLEX: New features, architectural changes, statistical implementations

4. Execute workflow based on tier:

FOR SIMPLE ISSUES: