develop

Develop

Bridges issue tracking and development workflow. Creates branches, manages work context.

Critical Rules

• Read cross-cutting behaviors first: skills/shared/references/cross-cutting.md
• Always view the issue first before starting development
• Worktree reuse: If already in a git worktree (e.g., claude -w), do NOT create a new branch — rename the current branch to match the issue and continue
• Check working tree for uncommitted changes before switching branches
• Add a comment to the issue when starting development
• Self-assign the issue when starting work (if not already assigned)

Prerequisites Check

gh auth status
git status

Capabilities

1. Start Development

Begin work on an issue: view it, create a branch, assign, and comment.

Workflow:

1. View the issue for context:

   gh issue view NUMBER --json number,title,body,labels,assignees,state
   

   Verify the issue is open. If closed, ask the user if they want to reopen it.

1b. Readiness review — delegate to the issue-reviewer agent to verify the issue has acceptance criteria and proper labels before starting development. Present the review results to the user. If the review fails, suggest refining the issue first using the refine skill.

1c. Detect worktree — check if already inside a git worktree:

if [ "$(git rev-parse --git-dir)" != "$(git rev-parse --git-common-dir)" ]; then
  echo "Inside a worktree"
fi

If in a worktree: skip steps 2-4 entirely. The current branch IS the development branch. Rename it to follow the NUMBER-slug convention if it doesn't already match:

# Only rename if current branch doesn't match NUMBER-* pattern
CURRENT=$(git branch --show-current)
TARGET="NUMBER-slugified-title"
if [ "$CURRENT" != "$TARGET" ]; then
  git branch -m "$TARGET"
fi

Then continue directly to step 5.

1. Check working tree:

   git status --porcelain
   

   If there are uncommitted changes, warn the user and ask how to proceed (stash, commit, or abort).