---
name: issue-review
effort: medium
description: Run the GitHub issue review workflow for triage and planning. Use when the user asks to review or triage a GitHub issue, requests the /issue-review slash command, or needs an issue summary with priority/plan/tests.
---

# Issue Review

## Overview

## Effort

**Baseline:** `effort: medium` (frontmatter). **Inline override:** pass
`effort=<low|medium|high|xhigh|max>` anywhere in the invocation to scale
reasoning depth for this run — detect it once at kickoff and strip the token
before consuming user input. Level→behavior mapping, parsing contract, and
precedence caveats: `framework/agents/effort-protocol.md`.


Run the `/issue-review` automation, capture issue context, and produce a triage + plan summary using the project's GitHub issue subagent protocol.

## Workflow

If the user mentions `/issue-review` without a number, ask for the GitHub issue ID.

### Phase 0 — Documentation Context

Before triaging, route through `${paths.references_dir}/ssot-registry.md` and `rg` over `${paths.references_dir}/`, `${paths.backlog_dir}/`, and `.claude/agents/` to find related PRDs, ADRs, and reference docs for the issue's domain. Verify implementation/stateful claims against repo docs/code. Check `${paths.references_dir}/traceability-matrix.md` for source-to-doc mappings.

### Phase 1 — Triage

1. Run `npm run issue-review <number>` (optionally `--repo owner/repo`). This calls `scripts/issue-review.mjs` to fetch the issue snapshot including structured JSON data.
2. Perform the clarity analysis in `agents/github-issue-subagent.md` (MUST for bugs per AGENTS.md).
3. Apply the triage matrix from `agents/github-issue-subagent.md`, listing Blocker/High impacts first.

### Phase 2 — Plan

4. Create or update a backlog card from `templates/feature-card.template.yml`. Populate `execution_mode`, `git_strategy`, and `claimed_paths` fields.
5. Ask the user which git strategy to use (main vs feature branch) per AGENTS.md and record it in `git_strategy`.
6. Route to specialist agents based on issue type:
   - UI/UX issues: invoke `ui-expert` agent.
   - New features (label "New Feature" or implicit): invoke `prd` agent, follow `agents/index.md` pre-implementation requirements.
   - Architecture decisions: invoke `codebase-architect` agent.

### Phase 3 — Execute

7. For new features: invoke `prd` agent for spec, synthesize plan into backlog card, invoke `coder` agent to implement.
8. For bugs/fixes: invoke `coder` agent for complex fixes.
9. After implementation: invoke `code-reviewer` on the changes (MUST per agents/index.md).
10. If documentation updates are needed: invoke `doc-reviewer`.
11. Apply `vibe review` label and add a summary comment on the GitHub issue (MUST per AGENTS.md).

## Agent Routing

Follow `agents/index.md` for agent invocation rules and sequencing. Do not write production code yourself; orchestrate other agents and synthesize results. Run independent agents in the background where possible.
