@su-record/vibe 2.8.52 → 2.9.1

package/skills/prioritization-frameworks/SKILL.md

@@ -1,87 +1,87 @@
----
-name: prioritization-frameworks
-tier: standard
-description: "Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more."
-triggers: [prioritize, prioritization, rice, ice, kano, moscow, opportunity score]
-priority: 50
-chain-next: [create-prd]
----
-
-# Prioritization Frameworks Reference
-
-> Based on the Product Frameworks Compendium from [Product Compass](https://www.productcompass.pm/p/the-product-frameworks-compendium) by Pawel Huryn (MIT License).
-
-A reference guide to help you select and apply the right prioritization framework for your context.
-
-## Core Principle
-
-Never allow customers to design solutions. Prioritize **problems (opportunities)**, not features.
-
-## Opportunity Score (Dan Olsen, *The Lean Product Playbook*)
-
-The recommended framework for prioritizing customer problems.
-
-Survey customers on **Importance** and **Satisfaction** for each need (normalize to 0-1 scale).
-
-Three related formulas:
-- **Current value** = Importance x Satisfaction
-- **Opportunity Score** = Importance x (1 - Satisfaction)
-- **Customer value created** = Importance x (S2 - S1), where S1 = satisfaction before, S2 = satisfaction after
-
-High Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot.
-
-## ICE Framework
-
-Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
-
-- **I** (Impact) = Opportunity Score x Number of Customers affected
-- **C** (Confidence) = How confident are we? (1-10). Accounts for risk.
-- **E** (Ease) = How easy is it to implement? (1-10). Accounts for economic factors.
-
-**Score** = I x C x E. Higher = prioritize first.
-
-## RICE Framework
-
-Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.
-
-- **R** (Reach) = Number of customers affected
-- **I** (Impact) = Opportunity Score (value per customer)
-- **C** (Confidence) = How confident are we? (0-100%)
-- **E** (Effort) = How much effort to implement? (person-months)
-
-**Score** = (R x I x C) / E
-
-## 9 Frameworks Overview
-
-| Framework | Best For | Key Insight |
-|-----------|----------|-------------|
-| Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management |
-| Impact vs Effort | Tasks/initiatives | Simple 2x2 — quick triage, not rigorous for strategic decisions |
-| Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty |
-| **Opportunity Score** | Customer problems | **Recommended.** Importance x (1 - Satisfaction). Normalize to 0-1. |
-| Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. |
-| Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. |
-| **ICE** | Ideas/initiatives | Impact x Confidence x Ease. Recommended for quick prioritization. |
-| **RICE** | Ideas at scale | (Reach x Impact x Confidence) / Effort. Adds Reach to ICE. |
-| MoSCoW | Requirements | Must/Should/Could/Won't. Caution: project management origin. |
-
-## How to Choose
-
-1. **Prioritizing customer problems?** → Opportunity Score
-2. **Quick initiative ranking?** → ICE
-3. **Large team with data?** → RICE
-4. **Understanding user expectations?** → Kano Model
-5. **Stakeholder alignment needed?** → Weighted Decision Matrix
-6. **Requirements scoping?** → MoSCoW (with caution)
-
-## Templates
-
-- [Opportunity Score intro (PDF)](https://drive.google.com/file/d/1ENbYPmk1i1AKO7UnfyTuULL5GucTVufW/view)
-- [Importance vs Satisfaction Template (Google Slides)](https://docs.google.com/presentation/d/1jg-LuF_3QHsf6f1nE1f98i4C0aulnRNMOO1jftgti8M/edit#slide=id.g796641d975_0_3)
-- [ICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-/edit?usp=share_link)
-- [RICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1S-6QpyOz5MCrV7B67LUWdZkAzn38Eahv/edit?usp=sharing)
-
-## Further Reading
-
-- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
-- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
+---
+name: prioritization-frameworks
+tier: standard
+description: "Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more."
+triggers: [prioritize, prioritization, rice, ice, kano, moscow, opportunity score]
+priority: 50
+chain-next: [create-prd]
+---
+
+# Prioritization Frameworks Reference
+
+> Based on the Product Frameworks Compendium from [Product Compass](https://www.productcompass.pm/p/the-product-frameworks-compendium) by Pawel Huryn (MIT License).
+
+A reference guide to help you select and apply the right prioritization framework for your context.
+
+## Core Principle
+
+Never allow customers to design solutions. Prioritize **problems (opportunities)**, not features.
+
+## Opportunity Score (Dan Olsen, *The Lean Product Playbook*)
+
+The recommended framework for prioritizing customer problems.
+
+Survey customers on **Importance** and **Satisfaction** for each need (normalize to 0-1 scale).
+
+Three related formulas:
+- **Current value** = Importance x Satisfaction
+- **Opportunity Score** = Importance x (1 - Satisfaction)
+- **Customer value created** = Importance x (S2 - S1), where S1 = satisfaction before, S2 = satisfaction after
+
+High Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot.
+
+## ICE Framework
+
+Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
+
+- **I** (Impact) = Opportunity Score x Number of Customers affected
+- **C** (Confidence) = How confident are we? (1-10). Accounts for risk.
+- **E** (Ease) = How easy is it to implement? (1-10). Accounts for economic factors.
+
+**Score** = I x C x E. Higher = prioritize first.
+
+## RICE Framework
+
+Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.
+
+- **R** (Reach) = Number of customers affected
+- **I** (Impact) = Opportunity Score (value per customer)
+- **C** (Confidence) = How confident are we? (0-100%)
+- **E** (Effort) = How much effort to implement? (person-months)
+
+**Score** = (R x I x C) / E
+
+## 9 Frameworks Overview
+
+| Framework | Best For | Key Insight |
+|-----------|----------|-------------|
+| Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management |
+| Impact vs Effort | Tasks/initiatives | Simple 2x2 — quick triage, not rigorous for strategic decisions |
+| Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty |
+| **Opportunity Score** | Customer problems | **Recommended.** Importance x (1 - Satisfaction). Normalize to 0-1. |
+| Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. |
+| Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. |
+| **ICE** | Ideas/initiatives | Impact x Confidence x Ease. Recommended for quick prioritization. |
+| **RICE** | Ideas at scale | (Reach x Impact x Confidence) / Effort. Adds Reach to ICE. |
+| MoSCoW | Requirements | Must/Should/Could/Won't. Caution: project management origin. |
+
+## How to Choose
+
+1. **Prioritizing customer problems?** → Opportunity Score
+2. **Quick initiative ranking?** → ICE
+3. **Large team with data?** → RICE
+4. **Understanding user expectations?** → Kano Model
+5. **Stakeholder alignment needed?** → Weighted Decision Matrix
+6. **Requirements scoping?** → MoSCoW (with caution)
+
+## Templates
+
+- [Opportunity Score intro (PDF)](https://drive.google.com/file/d/1ENbYPmk1i1AKO7UnfyTuULL5GucTVufW/view)
+- [Importance vs Satisfaction Template (Google Slides)](https://docs.google.com/presentation/d/1jg-LuF_3QHsf6f1nE1f98i4C0aulnRNMOO1jftgti8M/edit#slide=id.g796641d975_0_3)
+- [ICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-/edit?usp=share_link)
+- [RICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1S-6QpyOz5MCrV7B67LUWdZkAzn38Eahv/edit?usp=sharing)
+
+## Further Reading
+
+- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
+- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)

package/skills/prioritization-frameworks/rubrics/frameworks.md

@@ -1,79 +1,79 @@
-# Prioritization Frameworks Rubric
-
-## RICE
-
-**Formula**: `(Reach × Impact × Confidence) / Effort`
-
-| Factor | Scale | Example |
-|--------|-------|---------|
-| Reach | Users/month (absolute) | 5,000 users |
-| Impact | Opportunity Score 0.0–1.0 | 0.7 |
-| Confidence | 0–100% | 80% = 0.8 |
-| Effort | Person-months | 2 |
-
-**Example**: `(5000 × 0.7 × 0.8) / 2 = 1400` — higher score = prioritize first.
-
-**When to use**: Large teams with data. Separates audience size (Reach) from value per user (Impact).
-
-**Watch out for**: Effort estimates are often optimistic — apply a 1.5x buffer.
-
----
-
-## ICE
-
-**Formula**: `Impact × Confidence × Ease`
-
-| Factor | Scale | Example |
-|--------|-------|---------|
-| Impact | 1–10 (or Opportunity Score × Users) | 8 |
-| Confidence | 1–10 | 7 |
-| Ease | 1–10 (inverse of effort) | 5 |
-
-**Example**: `8 × 7 × 5 = 280` — higher score = prioritize first.
-
-**When to use**: Quick ranking of ideas/initiatives. Faster than RICE, good for early-stage decisions.
-
-**Watch out for**: "Ease" is subjective — calibrate across team before scoring.
-
----
-
-## MoSCoW
-
-**Categories**:
-
-| Category | Meaning | Guideline |
-|----------|---------|-----------|
-| **Must** | Cannot launch without | Max 60% of scope |
-| **Should** | High value, not critical | Next priority after Must |
-| **Could** | Nice to have | Include only if capacity allows |
-| **Won't** | Explicitly deferred | Documents what is NOT in scope |
-
-**When to use**: Scoping a release. Good for stakeholder alignment conversations.
-
-**Watch out for**: Stakeholders inflate "Must" — challenge each Must with "What happens if we skip this for V1?". MoSCoW is a scoping tool, not a discovery tool.
-
----
-
-## Opportunity Score
-
-**Formula**: `Importance × (1 − Satisfaction)` (normalize both to 0–1 scale)
-
-**Example**:
-- Importance: 0.9, Satisfaction: 0.3 → Score: `0.9 × 0.7 = 0.63` (high opportunity)
-- Importance: 0.9, Satisfaction: 0.9 → Score: `0.9 × 0.1 = 0.09` (already solved)
-
-**When to use**: Prioritizing customer problems before deciding on solutions. Prevents building features customers already find satisfactory.
-
-**Watch out for**: Survey sample must be representative. Low sample size inflates confidence.
-
----
-
-## Choosing the Right Framework
-
-| Situation | Recommended Framework |
-|-----------|----------------------|
-| "Which customer problems matter most?" | Opportunity Score |
-| "Which features should we build this sprint?" | ICE |
-| "How do we rank initiatives across a large team?" | RICE |
-| "What goes into V1 vs. later?" | MoSCoW |
-| "Stakeholders disagree on priorities?" | Weighted Decision Matrix |
+# Prioritization Frameworks Rubric
+
+## RICE
+
+**Formula**: `(Reach × Impact × Confidence) / Effort`
+
+| Factor | Scale | Example |
+|--------|-------|---------|
+| Reach | Users/month (absolute) | 5,000 users |
+| Impact | Opportunity Score 0.0–1.0 | 0.7 |
+| Confidence | 0–100% | 80% = 0.8 |
+| Effort | Person-months | 2 |
+
+**Example**: `(5000 × 0.7 × 0.8) / 2 = 1400` — higher score = prioritize first.
+
+**When to use**: Large teams with data. Separates audience size (Reach) from value per user (Impact).
+
+**Watch out for**: Effort estimates are often optimistic — apply a 1.5x buffer.
+
+---
+
+## ICE
+
+**Formula**: `Impact × Confidence × Ease`
+
+| Factor | Scale | Example |
+|--------|-------|---------|
+| Impact | 1–10 (or Opportunity Score × Users) | 8 |
+| Confidence | 1–10 | 7 |
+| Ease | 1–10 (inverse of effort) | 5 |
+
+**Example**: `8 × 7 × 5 = 280` — higher score = prioritize first.
+
+**When to use**: Quick ranking of ideas/initiatives. Faster than RICE, good for early-stage decisions.
+
+**Watch out for**: "Ease" is subjective — calibrate across team before scoring.
+
+---
+
+## MoSCoW
+
+**Categories**:
+
+| Category | Meaning | Guideline |
+|----------|---------|-----------|
+| **Must** | Cannot launch without | Max 60% of scope |
+| **Should** | High value, not critical | Next priority after Must |
+| **Could** | Nice to have | Include only if capacity allows |
+| **Won't** | Explicitly deferred | Documents what is NOT in scope |
+
+**When to use**: Scoping a release. Good for stakeholder alignment conversations.
+
+**Watch out for**: Stakeholders inflate "Must" — challenge each Must with "What happens if we skip this for V1?". MoSCoW is a scoping tool, not a discovery tool.
+
+---
+
+## Opportunity Score
+
+**Formula**: `Importance × (1 − Satisfaction)` (normalize both to 0–1 scale)
+
+**Example**:
+- Importance: 0.9, Satisfaction: 0.3 → Score: `0.9 × 0.7 = 0.63` (high opportunity)
+- Importance: 0.9, Satisfaction: 0.9 → Score: `0.9 × 0.1 = 0.09` (already solved)
+
+**When to use**: Prioritizing customer problems before deciding on solutions. Prevents building features customers already find satisfactory.
+
+**Watch out for**: Survey sample must be representative. Low sample size inflates confidence.
+
+---
+
+## Choosing the Right Framework
+
+| Situation | Recommended Framework |
+|-----------|----------------------|
+| "Which customer problems matter most?" | Opportunity Score |
+| "Which features should we build this sprint?" | ICE |
+| "How do we rank initiatives across a large team?" | RICE |
+| "What goes into V1 vs. later?" | MoSCoW |
+| "Stakeholders disagree on priorities?" | Weighted Decision Matrix |

package/skills/prioritization-frameworks/templates/scoring-matrix.md

@@ -1,69 +1,69 @@
-# Prioritization Scoring Matrix Template
-
-## Project / Sprint: {{PROJECT_OR_SPRINT_NAME}}
-
-**Framework selected**: {{FRAMEWORK}} (RICE / ICE / MoSCoW / Opportunity Score)
-**Date**: {{DATE}}
-**Scored by**: {{SCORER_NAMES}}
-
----
-
-## RICE Scoring Matrix
-
-| Item | Reach (users/mo) | Impact (0–1) | Confidence (%) | Effort (person-mo) | RICE Score | Priority |
-|------|-----------------|--------------|----------------|--------------------|------------|----------|
-| {{ITEM_1}} | {{R}} | {{I}} | {{C}} | {{E}} | `=(R×I×C)/E` | — |
-| {{ITEM_2}} | {{R}} | {{I}} | {{C}} | {{E}} | `=(R×I×C)/E` | — |
-| {{ITEM_3}} | {{R}} | {{I}} | {{C}} | {{E}} | `=(R×I×C)/E` | — |
-
----
-
-## ICE Scoring Matrix
-
-| Item | Impact (1–10) | Confidence (1–10) | Ease (1–10) | ICE Score | Priority |
-|------|---------------|-------------------|-------------|-----------|----------|
-| {{ITEM_1}} | {{I}} | {{C}} | {{E}} | `=I×C×E` | — |
-| {{ITEM_2}} | {{I}} | {{C}} | {{E}} | `=I×C×E` | — |
-| {{ITEM_3}} | {{I}} | {{C}} | {{E}} | `=I×C×E` | — |
-
----
-
-## MoSCoW Categorization
-
-| Item | Category | Rationale | Owner |
-|------|----------|-----------|-------|
-| {{ITEM_1}} | Must / Should / Could / Won't | {{REASON}} | {{OWNER}} |
-| {{ITEM_2}} | Must / Should / Could / Won't | {{REASON}} | {{OWNER}} |
-| {{ITEM_3}} | Must / Should / Could / Won't | {{REASON}} | {{OWNER}} |
-
-**Must count**: {{X}} / {{TOTAL}} — keep Must ≤ 60% of total scope.
-
----
-
-## Opportunity Score Matrix
-
-| Customer Need | Importance (0–1) | Satisfaction (0–1) | Opportunity Score | Action |
-|--------------|------------------|---------------------|-------------------|--------|
-| {{NEED_1}} | {{I}} | {{S}} | `=I×(1-S)` | Invest / Monitor / Maintain |
-| {{NEED_2}} | {{I}} | {{S}} | `=I×(1-S)` | Invest / Monitor / Maintain |
-| {{NEED_3}} | {{I}} | {{S}} | `=I×(1-S)` | Invest / Monitor / Maintain |
-
-Score > 0.5 = strong opportunity. Score < 0.1 = already solved.
-
----
-
-## Final Ranked Backlog
-
-| Rank | Item | Framework Score | Decision | Notes |
-|------|------|-----------------|----------|-------|
-| 1 | {{ITEM}} | {{SCORE}} | Build / Defer / Drop | {{NOTES}} |
-| 2 | {{ITEM}} | {{SCORE}} | Build / Defer / Drop | {{NOTES}} |
-| 3 | {{ITEM}} | {{SCORE}} | Build / Defer / Drop | {{NOTES}} |
-
----
-
-## Scoring Notes
-
-- {{ASSUMPTION_OR_CAVEAT_1}}
-- {{ASSUMPTION_OR_CAVEAT_2}}
-- Next review date: {{REVIEW_DATE}}
+# Prioritization Scoring Matrix Template
+
+## Project / Sprint: {{PROJECT_OR_SPRINT_NAME}}
+
+**Framework selected**: {{FRAMEWORK}} (RICE / ICE / MoSCoW / Opportunity Score)
+**Date**: {{DATE}}
+**Scored by**: {{SCORER_NAMES}}
+
+---
+
+## RICE Scoring Matrix
+
+| Item | Reach (users/mo) | Impact (0–1) | Confidence (%) | Effort (person-mo) | RICE Score | Priority |
+|------|-----------------|--------------|----------------|--------------------|------------|----------|
+| {{ITEM_1}} | {{R}} | {{I}} | {{C}} | {{E}} | `=(R×I×C)/E` | — |
+| {{ITEM_2}} | {{R}} | {{I}} | {{C}} | {{E}} | `=(R×I×C)/E` | — |
+| {{ITEM_3}} | {{R}} | {{I}} | {{C}} | {{E}} | `=(R×I×C)/E` | — |
+
+---
+
+## ICE Scoring Matrix
+
+| Item | Impact (1–10) | Confidence (1–10) | Ease (1–10) | ICE Score | Priority |
+|------|---------------|-------------------|-------------|-----------|----------|
+| {{ITEM_1}} | {{I}} | {{C}} | {{E}} | `=I×C×E` | — |
+| {{ITEM_2}} | {{I}} | {{C}} | {{E}} | `=I×C×E` | — |
+| {{ITEM_3}} | {{I}} | {{C}} | {{E}} | `=I×C×E` | — |
+
+---
+
+## MoSCoW Categorization
+
+| Item | Category | Rationale | Owner |
+|------|----------|-----------|-------|
+| {{ITEM_1}} | Must / Should / Could / Won't | {{REASON}} | {{OWNER}} |
+| {{ITEM_2}} | Must / Should / Could / Won't | {{REASON}} | {{OWNER}} |
+| {{ITEM_3}} | Must / Should / Could / Won't | {{REASON}} | {{OWNER}} |
+
+**Must count**: {{X}} / {{TOTAL}} — keep Must ≤ 60% of total scope.
+
+---
+
+## Opportunity Score Matrix
+
+| Customer Need | Importance (0–1) | Satisfaction (0–1) | Opportunity Score | Action |
+|--------------|------------------|---------------------|-------------------|--------|
+| {{NEED_1}} | {{I}} | {{S}} | `=I×(1-S)` | Invest / Monitor / Maintain |
+| {{NEED_2}} | {{I}} | {{S}} | `=I×(1-S)` | Invest / Monitor / Maintain |
+| {{NEED_3}} | {{I}} | {{S}} | `=I×(1-S)` | Invest / Monitor / Maintain |
+
+Score > 0.5 = strong opportunity. Score < 0.1 = already solved.
+
+---
+
+## Final Ranked Backlog
+
+| Rank | Item | Framework Score | Decision | Notes |
+|------|------|-----------------|----------|-------|
+| 1 | {{ITEM}} | {{SCORE}} | Build / Defer / Drop | {{NOTES}} |
+| 2 | {{ITEM}} | {{SCORE}} | Build / Defer / Drop | {{NOTES}} |
+| 3 | {{ITEM}} | {{SCORE}} | Build / Defer / Drop | {{NOTES}} |
+
+---
+
+## Scoring Notes
+
+- {{ASSUMPTION_OR_CAVEAT_1}}
+- {{ASSUMPTION_OR_CAVEAT_2}}
+- Next review date: {{REVIEW_DATE}}

package/skills/priority-todos/SKILL.md

@@ -1,64 +1,64 @@
----
-name: priority-todos
-tier: standard
-description: "Priority-based TODO management (P1/P2/P3). Auto-activates when managing tasks, reviewing issues, or organizing work by priority."
-triggers: [todo, priority, P1, P2, P3, task management, issue, organize]
-priority: 60
----
-
-# Priority-Based Todo Management
-
-## Pre-check (K1)
-
-> Do you need structured priority tracking? For 1-2 item task lists, use inline TODOs. This system is for multi-issue tracking across reviews and sessions.
-
-## Priority Definitions
-
-| Priority | Meaning | Action | Examples |
-|----------|---------|--------|----------|
-| P1 | **Blocks merge** | Fix immediately | Security vulnerability, data loss risk, production incident |
-| P2 | **Should fix** | Fix before PR | Performance issue, missing tests, architecture violation |
-| P3 | **Backlog** | Fix when time permits | Code style, refactoring suggestion, documentation |
-
-## Directory Structure
-
-```
-.claude/vibe/todos/
-├── P1-security-sql-injection.md
-├── P2-perf-n1-query.md
-├── P3-style-extract-helper.md
-├── index.md                      # Summary table with counts/status
-└── done/                         # Archived completed items
-```
-
-## Workflow
-
-```
-/vibe.review → Creates P1/P2/P3 todo files + updates index.md
-     ↓
-Fix P1 first (blocks merge)
-     ↓
-Fix P2 before PR (warning only)
-     ↓
-P3 → backlog (weekly review)
-     ↓
-Mark done → moves to done/ with date prefix
-```
-
-## Todo File Format
-
-Each file follows: `# [P1] Title` → Summary → Priority Justification → Location (file:line) → Suggested Fix → Checklist (fix, test, review, merge).
-
-## Rules
-
-- P1 exists → merge is **blocked**
-- P2 → warning only, recommended to resolve
-- P3 → no blocking, backlog
-- Weekly cleanup: review and archive completed items
-
-## Done Criteria (K4)
-
-- [ ] All P1 items resolved before merge
-- [ ] P2 items reviewed and either resolved or documented
-- [ ] index.md reflects current state
-- [ ] Completed items archived to `done/` directory
+---
+name: priority-todos
+tier: standard
+description: "Priority-based TODO management (P1/P2/P3). Auto-activates when managing tasks, reviewing issues, or organizing work by priority."
+triggers: [todo, priority, P1, P2, P3, task management, issue, organize]
+priority: 60
+---
+
+# Priority-Based Todo Management
+
+## Pre-check (K1)
+
+> Do you need structured priority tracking? For 1-2 item task lists, use inline TODOs. This system is for multi-issue tracking across reviews and sessions.
+
+## Priority Definitions
+
+| Priority | Meaning | Action | Examples |
+|----------|---------|--------|----------|
+| P1 | **Blocks merge** | Fix immediately | Security vulnerability, data loss risk, production incident |
+| P2 | **Should fix** | Fix before PR | Performance issue, missing tests, architecture violation |
+| P3 | **Backlog** | Fix when time permits | Code style, refactoring suggestion, documentation |
+
+## Directory Structure
+
+```
+.claude/vibe/todos/
+├── P1-security-sql-injection.md
+├── P2-perf-n1-query.md
+├── P3-style-extract-helper.md
+├── index.md                      # Summary table with counts/status
+└── done/                         # Archived completed items
+```
+
+## Workflow
+
+```
+/vibe.review → Creates P1/P2/P3 todo files + updates index.md
+     ↓
+Fix P1 first (blocks merge)
+     ↓
+Fix P2 before PR (warning only)
+     ↓
+P3 → backlog (weekly review)
+     ↓
+Mark done → moves to done/ with date prefix
+```
+
+## Todo File Format
+
+Each file follows: `# [P1] Title` → Summary → Priority Justification → Location (file:line) → Suggested Fix → Checklist (fix, test, review, merge).
+
+## Rules
+
+- P1 exists → merge is **blocked**
+- P2 → warning only, recommended to resolve
+- P3 → no blocking, backlog
+- Weekly cleanup: review and archive completed items
+
+## Done Criteria (K4)
+
+- [ ] All P1 items resolved before merge
+- [ ] P2 items reviewed and either resolved or documented
+- [ ] index.md reflects current state
+- [ ] Completed items archived to `done/` directory