# Project Fix Plan Skill

## Trigger
`/project-fix [absolute_path]` or "수정 계획", "개선 플랜"

## Description
Creates a prioritized action plan from audit findings. Groups fixes by urgency and effort.

## Priority Framework (Eisenhower Matrix for Code)

| | Low Effort | High Effort |
|---|-----------|-------------|
| **Critical** | 🔴 DO NOW (Sprint 0) | 🟠 PLAN (Sprint 1-2) |
| **Important** | 🟡 SCHEDULE (Sprint 1) | ⚪ BACKLOG |

## Categorization Rules
- **Critical**: Security vulnerabilities, data loss risk, production blockers
- **Important**: Architecture violations, performance bottlenecks, test gaps
- **Low Effort**: < 2 hours, single file change
- **High Effort**: > 1 day, multi-file refactor

## Output Format
Final deliverable in **Korean (한국어)**.

```markdown
# [Project Name] Fix Plan

## 🔴 Sprint 0 — 즉시 (이번 주)
| # | Finding | File | Effort | Agent |
|---|---------|------|--------|-------|
| 1 | | | ~Xh | Security |

## 🟠 Sprint 1 — 계획 (다음 2주)
| # | Finding | Files | Effort | Agent |
|---|---------|-------|--------|-------|

## 🟡 Sprint 2 — 예정 (이번 달)
| # | Finding | Scope | Effort | Agent |
|---|---------|-------|--------|-------|

## ⚪ Backlog — 여유 시 진행
| # | Finding | Scope | Effort | Agent |
|---|---------|-------|--------|-------|

## Estimated Total Effort
- Sprint 0: ~X hours
- Sprint 1: ~X days
- Sprint 2: ~X days
- Backlog: ~X days

## Expected Score Improvement
| Dimension | Current | After Sprint 0 | After Sprint 1 |
|-----------|---------|----------------|----------------|
```

## Brutal Analysis Principles
- Critical security fixes cannot be pushed to backlog — ever
- Effort estimates must be realistic for a solo developer

## Claude-Gemini Cross-Debate Protocol
Priority classification disagreements are debated. Effort estimates are averaged.