--- name: implement-issue description: Dispatch a child agent in an isolated git worktree to implement a `ready-for-agent` issue end-to-end. disable-model-invocation: true --- # Implement Issue Dispatch a child agent in an isolated git worktree to implement a `ready-for-agent` issue end-to-end — explore, implement with TDD, run the full quality gate, push a branch, create a PR, comment on the issue, and update labels. The issue tracker conventions live in [`docs/agents/issue-tracker.md`](../../../docs/agents/issue-tracker.md) and the triage label vocabulary in [`docs/agents/triage-labels.md`](../../../docs/agents/triage-labels.md). Both should have been provided to you already. ## Invocation ``` /skill:implement-issue [--agent ] [--base ] [--force] ``` - `` — required, the issue number - `--agent ` — optional, one of `pi`, `opencode`, `goose`, `codex`, `claude`. If omitted, auto-detected from the process tree. - `--base ` — optional, target base branch (default: repo default branch). - `--force` — optional, allow overwriting an existing worktree. ## Process ### 1. Pre-flight checks Stop on any failure and report clearly what needs fixing. Do not proceed. #### 1a. `tea` CLI Confirm `tea` is on PATH. If missing, tell the user to install it and stop. #### 1b. Issue exists and is open ```bash tea issue -o json ``` If the issue is not found (404) or state is not `open`, report and stop. #### 1c. Issue is labeled `ready-for-agent` Check that the issue's labels include `ready-for-agent`. If not, report the current state and point the user to `/triage`. Stop. #### 1d. No open blockers Read the issue body for "Blocked by #M" references. For each referenced issue, check whether it is open: ```bash tea issue -o json ``` If any blocker is open, report the blocking issues and stop. #### 1e. Remote exists and base branch is reachable Default base is the repo's default branch — infer from `git ls-remote --heads origin` (look for `main` or `master`). Allow an explicit `--base ` override. ```bash git ls-remote --heads origin ``` If the remote is unreachable or the base branch doesn't exist, report and stop. SSH auth issues (e.g. `Permission denied (publickey)`) are a failure — tell the user which key is needed. > **SSH note:** `tea` uses HTTPS and may work when git-over-SSH does not. If the first `git ls-remote` fails with an SSH error, try `export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)` and retry before failing. #### 1f. Branch name is free Derive the branch name from the issue title: - Format: `issue--` - Slug: lowercase the title, strip to `[a-z0-9-]`, truncate to ~4–5 short words (max ~50 chars), collapse double hyphens - If the title yields no usable slug, fall back to `issue-` Check that the branch doesn't already exist on the remote: ```bash git ls-remote --heads origin ``` If it exists, report and stop. (No auto-suffix, no force-push.) #### 1g. Worktree path is free The worktree path is a sibling to the main repo: `../-issue-`. Check that it doesn't already exist: ```bash ls -d ../-issue- ``` If it exists, report and stop. Let the user override with `--force`. #### 1h. Running inside a tmux session Confirm `$TMUX` is set. If not, report "This skill requires a tmux session. Start tmux and rerun." and stop. #### 1i. Detect the agent binary If `--agent ` was provided in the invocation args, use that name directly. Otherwise, run the platform-appropriate detection script: ```bash bash ./detect-agent-linux.sh # or on macOS: bash ./detect-agent-macos.sh ``` The script outputs the agent name on success (exit 0), or nothing on failure (exit 1). If detection fails (no `--agent` flag and script returns nothing), report: > Could not detect which agent is running. Rerun with `--agent `. > Supported agents: pi, opencode, goose, codex, claude. Stop. If detection succeeds, confirm the binary is on PATH: ```bash command -v ``` If the binary is not found, report "Agent binary '' not found on PATH." and stop. ### 2. Setup #### 2a. Fetch latest base ```bash git fetch origin ``` #### 2b. Label the issue `in-progress` ```bash tea issues edit --add-labels "in-progress" --remove-labels "ready-for-agent" ``` #### 2c. Create the worktree ```bash git worktree add -b ../-issue- ``` ### 3. Compose and write the child prompt Assemble a single prompt that the child agent will receive. Include: - **Issue body** — the full markdown body from `tea issue -o json` - **Comments** — all comments, if any - **Standing instruction**: "Implement using TDD: write a failing test first, make it pass, refactor. Explore the codebase before writing code. Respect ADRs and the project domain glossary. Set up the project (install dependencies, build) before starting. The issue body may contain Implementation Decisions and Testing Decisions sections — treat these as constraints." - **Context**: "Base branch: ``. Target your PR at ``. Branch name: ``." - **Checklist** — a numbered checklist the child should work through: 1. Explore the codebase and read the issue body + comments thoroughly 2. Install dependencies and build the project 3. Implement the change using TDD (red-green-refactor) 4. Run the full project quality gate (infer from package.json, Makefile, Cargo.toml, etc.), fix until green 5. Commit with conventional commits (`feat:` for enhancement, `fix:` for bug) referencing `(#)` 6. Push the branch: `git push origin ` 7. Create a PR with: link to the issue, one-sentence summary, short key-changes list 8. Comment on the issue with the PR link: `tea comment "PR opened: "` 9. Change the issue label to `needs-review`: `tea issues edit --add-labels "needs-review" --remove-labels "in-progress"` 10. Print `DONE — issue #` - **Failure instruction**: "If any step fails, report where you stopped and what remains for manual recovery. Print the exact commands needed." Write the full prompt to a temp file: ```bash cat > /tmp/issue--prompt.md <<'PROMPT_EOF' PROMPT_EOF ``` ### 4. Launch the child Look up the full shell command from the dispatch table below, using the agent name detected in step 1i. | Agent | Shell command | |-------|--------------| | `pi` | `pi -p @/tmp/issue--prompt.md` | | `opencode` | `opencode run -f /tmp/issue--prompt.md` | | `goose` | `goose run -i /tmp/issue--prompt.md` | | `codex` | `cat /tmp/issue--prompt.md \| codex exec` | | `claude` | `cat /tmp/issue--prompt.md \| claude -p` | | *unknown* | `cat /tmp/issue--prompt.md \| ` | Substitute the actual temp file path and issue number, then launch in a new tmux window: ```bash tmux new-window -n "issue--" -c "" ``` For example, with pi: ```bash tmux new-window -n "issue-42-myrepo" -c ../myrepo-issue-42 "pi -p @/tmp/issue-42-prompt.md" ``` The window stays open after the child completes so the user can review the output. After tmux launches, clean up the temp file: ```bash rm /tmp/issue--prompt.md ``` ### 5. Print summary After launching, print: - Issue number and title - Worktree path - Branch name - Base branch - Agent used - Tmux window name (so the user can find it) - Cleanup command: `git worktree remove && git worktree prune` The parent's turn ends here. The user can dispatch another issue immediately.