decide_bug_task_plan - Claude MCP Skill

# Decide: Bug Task Plan

## D8: Generate Complete Plan for Spec Adjustments to Drive Bug Fix

Based on bug analysis and spec adjustment strategy:
- What acceptance criteria need to be added or corrected?
- What edge cases need to be documented?
- What error conditions need to be specified?
- What clarifications need to be made?
- What examples need to be added to prevent regression?
- What data structure constraints need to be tightened?

Generate a complete plan - don't incrementally patch. Plans are disposable.

## D9: Structure Plan by Priority (Most Important First)

Order the tasks:
- What must be done first? (critical spec gaps that caused the bug)
- What depends on other tasks?
- What can be parallelized?
- What has highest impact on preventing regression?
- What blocks the actual bug fix implementation?

## D10: Break into Tight, Actionable Tasks

For each item in the plan:
- Is it small enough for one iteration? (tight task)
- Is it clearly defined? (actionable)
- Does it have clear acceptance criteria?
- Can it be verified when complete?
- If too large, break it down further

One task per build iteration maximizes smart zone utilization.

## D11: Determine Task Dependencies

For each task:
- What other tasks must complete first?
- What tasks can run in parallel?
- What tasks block the bug fix implementation?
- Document dependencies explicitly