fix-feature-bug

Fix Feature Bug

Systematically fix bugs using error classification and regression testing.

When to Use

Use this skill when:

• User mentions "bug", "error", "fix", "broken", "not working", "failing"
• User reports "issue" or "problem" in context of code/functionality
• Error messages or stack traces are present
• Test failures mentioned
• User mentions "regression" or "broken feature"
• User explicitly invokes /fix-feature-bug

Workflow

Step 1: Detection and Confirmation

1. Extract bug information from context:

   • Error messages or stack traces (if provided)
   • Feature/module ID (if mentioned or inferred from paths)
   • Description of the problem
   • Steps to reproduce (if mentioned)

2. Identify affected feature/module:

   • Check error messages for file paths
   • Check context for feature mentions
   • Check open files for feature references
   • If cannot identify → ask: "Which feature/module is affected? (identifier or 'unknown')"

3. Ask for confirmation:

   I see you're reporting a bug. Should I fix this using the bug fix workflow? 
   Feature/Module: {identifier} (or 'unknown' if not identified)
   (yes/no)
   

4. Handle exceptions:

   • If user says "no" → do not proceed
   • If user says "just document it" → document the bug instead of fixing

Step 2: Execute Bug Fix Workflow

If user confirms (yes):

1. Load configuration:

   • Read foundation-config.yaml for bug fix workflow settings
   • Check if development.bug_fix.error_classification.enabled is true
   • Determine feature unit directory (if feature units enabled)

2. Load required documents:

   • foundation/agent_instructions/cursor_commands/fix_feature_bug.md — workflow
   • Repository navigation guide (if configured)
   • Feature spec and manifest (if feature units enabled and identifier provided)
   • Error classification documentation (if configured)
   • Relevant subsystem/module docs (if configured)

3. Classify bug (if error classification configured):

   • Class 1: Implementation bug (spec correct, code wrong) → Patch code only
   • Class 2: Spec bug (code correct, spec wrong) → Update spec first, then align code
   • Class 3: Architectural bug (architecture docs wrong) → Update architecture docs first