bug-plan

Bug Plan

Configuration Required: This skill requires project configuration. If .claude/bugflow/config/environment.json does not exist, prompt the user to run /bugflow:bug-setup first.

Table of Contents

• Command
• Prerequisites
• Process Overview
• Agents Used
• State Flow
• Outputs
• Revision Rules
• Reference

Generate a minimal-risk frontend implementation plan with history-aware revision loop.

Command

/bug-plan <bug_id> - Generate or revise implementation plan for a bug

Prerequisites

• Bug workflow must be started (state file exists)
• Verdict must be FE or MIXED (not BE-only)
• State must be: VERDICT, VERIFY_FAIL, PLAN_FE, or VALIDATE

---

Process Overview

1. Validate - Confirm state is ready for planning (FE/MIXED verdict)
2. Load History - Prior plans + rejection reasons + anti-patterns (if any)
3. Generate - Use fe-implementer-planner agent for minimal-risk plan
4. Test Spec - Use test-spec-generator agent to create tests
5. Validate - Use plan-validator agent (pass: score >= 70)
6. Report - Display plan for user approval

On validation failure: Archive plan, extract anti-patterns, loop (max 3). See REVISION-LOOP.md.

---

Agents Used

Agent	Purpose
fe-implementer-planner	Generate minimal-risk implementation plan
test-spec-generator	Generate structured test specification
plan-validator	Validate plan quality (pass: score >= 70)

---

State Flow

VERDICT/VERIFY_FAIL
        ↓
    [Planning Loop]
        ↓
   score >= 70?
      /    \
   YES      NO → [Archive + Extract anti-patterns]
    ↓              ↓
VALIDATE     [Loop again, max 3]
    ↓              ↓
  DONE        AWAITING_APPROVAL (escalate)

---

Outputs

Output	Path
Dossier	<paths.dossierDir> from project config (default: docs/bugflow)/bug-.md (IMPLEMENTATION STRATEGY section)
State	<paths.stateDir> from project config (default: .bugflow)//state.json
Plan	<paths.stateDir> from project config (default: .bugflow)//context/plan.json
History	<paths.stateDir> from project config (default: .bugflow)//context/plan-history/*.json

Revision Rules

• Max revisions: 3 iterations
• Improvement required: 10 points per revision
• If max reached: Escalate to AWAITING_APPROVAL for manual review

---

Reference

• PLANNING.md - Read for detailed planning steps, agent context, and JSON schemas
• VALIDATION.md - Read for validation criteria, scoring breakdown, and common failures
• REVISION-LOOP.md - Read for revision mechanics, anti-pattern extraction, and escalation