Bug Create Command

Initialize a new bug fix workflow for tracking and resolving bugs.

Usage

/bug-create <bug-name> [description]

Workflow Overview

This is the streamlined bug fix workflow - a lighter alternative to the full spec workflow for addressing bugs and issues.

Bug Fix Phases

Report Phase (This command) - Document the bug
Analysis Phase (/bug-analyze) - Investigate root cause
Fix Phase (/bug-fix) - Implement solution
Verification Phase (/bug-verify) - Confirm resolution

Instructions

You are helping create a new bug fix workflow. This is designed for smaller fixes that don't need the full spec workflow overhead.

Create Directory Structure
- Create .claude/bugs/{bug-name}/ directory
- Initialize report.md, analysis.md, and verification.md files

Load ALL Context Once (Hierarchical Context Loading) Load complete context at the beginning for the bug creation process:

# Load steering documents (if available)
claude-code-spec-workflow get-steering-context

# Load bug templates
claude-code-spec-workflow get-template-context bug

Gather Bug Information
- Take the bug name and optional description
- Guide user through bug report creation
- Use structured format for consistency
Generate Bug Report
- Template to Follow: Use the bug report template from the pre-loaded context above (do not reload)
- Create detailed bug description following the bug report template structure

Template Usage

Follow exact structure: Use loaded bug report template precisely
Include all sections: Don't omit any required template sections
Structured format: Follow the template's format for consistency

Request User Input
- Ask for bug details if not provided in description
- Guide through each section of the bug report
- Ensure all required information is captured
Save and Proceed
- Save the completed bug report to report.md
- Ask: "Is this bug report accurate? If so, we can move on to the analysis."
- Wait for explicit approval before proceeding

Key Differences from Spec Workflow

Faster: No requirements/design phases
Targeted: Focus on fixing existing functionality
Streamlined: 4 phases instead of detailed workflow
Practical: Direct from problem to solution

Rules

Only create ONE bug fix at a time
Always use kebab-case for bug names
Must analyze existing codebase during investigation
Follow existing project patterns and conventions
Do not proceed without user approval between phases

Error Handling

If issues arise during the workflow:

Bug unclear: Ask targeted questions to clarify
Too complex: Suggest breaking into smaller bugs or using spec workflow
Reproduction blocked: Document blockers and suggest alternatives

Example

/bug-create login-timeout "Users getting logged out too quickly"

Next Steps

After bug report approval, proceed to /bug-analyze phase.

/bug-create Command