bug

Session Start Check (required)

If session-start has not run in this session, run /atdd-kit:session-start first.

Bug Report Pipeline

Drives a bug report through Issue creation → reproduction → evidence collection → fix proposal.

Auto-trigger Conditions

• User reports "bug", "broken", "crash", "error", "not working", "display issue", etc.
• Japanese keywords: "バグ", "不具合", "おかしい", "壊れている", "動かない", "表示がおかしい", "落ちる", "クラッシュ", "エラー", "止まる", "反応しない", "フリーズ"
• Screenshots or videos attached
• Existing Issue with type:bug label and user requests a fix

When unsure, ask: "Should I triage this as a bug report?"

Phase 1: Intake

Ask one question at a time: (1) What happened? (2) What did you expect? (3) Steps to reproduce? (4) Environment? (5) Screenshots or logs?

Phase 2: Issue Creation

Create Issue using ${CLAUDE_PLUGIN_ROOT}/templates/issue/en/bug-report.yml (-ja.yml is human-only). Register with gh issue create. Do NOT add in-progress label.

Context Block Output

After creating the Issue, post a Context Block as an Issue comment:

## Context Block

| Field | Value |
|-------|-------|
| task_type | bug |
| symptom | [what is happening] |
| reproduction | [steps to reproduce] |
| environment | [OS, device, version] |
| expected | [what should happen] |
| collected_info | [screenshots, logs, stack traces] |

Enables defining-requirements to skip questions already answered during intake.

Phase 3: Existing Test Check

Search for and run related tests. Record results as Issue comment.

Phase 4: Reproduction

Read platform from .claude/config.yml. Reproduce on each applicable platform. Record evidence as Issue comment; ask for more info if not reproduced.

Phase 5: Evidence Collection

Bug Nature	Evidence Type
State issue (wrong display, stale data)	Screenshot
Action issue (crash on tap, navigation failure)	Screen recording
All bugs	Log capture + stack trace

Post evidence as Issue comment.

Spec Citation in Root Cause Classification

Before Classification, load the spec via bash lib/spec_check.sh derive_slug <issue> then spec_exists. Cite spec AC if present; on absent, emit [spec-warn] missing: ... and classify as A (AC Gap) with no spec found for <area> — never invent ad-hoc ACs. Continuation-fallback follows the shared AC6 matrix; see docs/guides/spec-reference.md.

Fix Proposal Format

## Fix Proposal

**Classification:** A/B/C -- <explanation citing spec AC or "no spec found for <area>">
**Spec AC:** docs/specs/<slug>.md#ACN (or "none — Classification A")
**Root Cause:** <what is broken and why>
**Fix Location:** <file:line>
**Parallel Patterns:** <N occurrences found / none>
**Effort:** Small / Medium / Large
**User Impact:** High / Medium / Low -- <reason>

AskUserQuestion — header: "Fix?", options: "(Recommended) Proceed with fix", "Revise proposal"

Recommended: Proceed with fix — reply 'ok' to accept, or provide alternative

Next Step

Show "Initial bug triage complete." and invoke the defining-requirements skill via the Skill tool (the bug chain routes into Step 1 of the 6-step flow).