superkit-mcp-server 1.2.2 → 1.2.3

package/skills/workflows/triage-sprint.md

@@ -1,102 +1,102 @@
----
-description: Batch process pending todos to unblock triage bottlenecks
----
-
-# /triage-sprint - Batch Triage Workflow
-
-Rapidly process pending work items with strict time-boxing to clear backlog bottlenecks.
-
-> **Why sprint?** When pending todos accumulate (e.g., >20 pending), individual triage is too slow. Sprints prioritize volume processing over deep analysis to restore flow.
-
-## When To Use
-
-- When "Pending Todos" count > 20
-- Weekly (Fridays) to clear the deck
-- When `compound-dashboard.sh` shows "Bottleneck" warning
-
----
-
-## Workflow
-
-### Step 0: Search Before Solving
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/triage-sprint", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "triage" "prioritization"] }
-```
-
----
-
-### Step 1: Assess Backlog
-
-Check the volume of work:
-
-```bash
-echo "Pending Todos: $(grep -l "Status: Pending" todos/*.md | wc -l)"
-```
-
-**Set Goal:**
-- 5 items = 10 minutes
-- 10 items = 20 minutes
-- 20+ items = 45 minutes (Max)
-
----
-
-### Step 2: Batch Processing (Sprint)
-
-Execute this block for each batch of 5 items:
-
-1. **List next 5 pending files:**
-   ```bash
-   ls todos/*-pending-*.md | head -5
-   ```
-
-2. **Rapid Review (2 min/item max):**
-   For each item, decide immediately:
-   - **Do Now:** Move to `/work` queue (Change status to `Ready`, set priority)
-   - **Defer:** Move to backlog (Change status to `Deferred`, add reason)
-   - **Reject:** Archive (Change status to `Archived`, add reason)
-   - **Duplicate:** Merge with existing (Archive one, update other)
-
-3. **Validation Command:**
-   ```bash
-   # Update status in file
-   sed -i '' 's/Status: Pending/Status: Ready/' todos/{filename}
-   # OR
-   sed -i '' 's/Status: Pending/Status: Deferred/' todos/{filename}
-   ```
-
----
-
-### Step 3: Hard Stop
-
-When time limit is reached:
-1. Stop processing
-2. Count remaining items
-3. Schedule next sprint if > 10 remain
-
----
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Triage Sprint",
-  TaskStatus: "Sprint complete. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Processed X items. Y remain pending. Z moved to Ready."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Sprint complete
-
-Next steps:
-1. /work - Start working on items marked Ready
-2. /housekeeping - Archive rejected items
-```
+---
+description: Batch process pending todos to unblock triage bottlenecks
+---
+
+# /triage-sprint - Batch Triage Workflow
+
+Rapidly process pending work items with strict time-boxing to clear backlog bottlenecks.
+
+> **Why sprint?** When pending todos accumulate (e.g., >20 pending), individual triage is too slow. Sprints prioritize volume processing over deep analysis to restore flow.
+
+## When To Use
+
+- When "Pending Todos" count > 20
+- Weekly (Fridays) to clear the deck
+- When MCP `call_tool_compound_manager` { action: "dashboard" } shows "Bottleneck" warning
+
+---
+
+## Workflow
+
+### Step 0: Search Before Solving
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/triage-sprint", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "triage" "prioritization"] }
+```
+
+---
+
+### Step 1: Assess Backlog
+
+Check the volume of work:
+
+```bash
+echo "Pending Todos: $(grep -l "Status: Pending" todos/*.md | wc -l)"
+```
+
+**Set Goal:**
+- 5 items = 10 minutes
+- 10 items = 20 minutes
+- 20+ items = 45 minutes (Max)
+
+---
+
+### Step 2: Batch Processing (Sprint)
+
+Execute this block for each batch of 5 items:
+
+1. **List next 5 pending files:**
+   ```bash
+   ls todos/*-pending-*.md | head -5
+   ```
+
+2. **Rapid Review (2 min/item max):**
+   For each item, decide immediately:
+   - **Do Now:** Move to `/work` queue (Change status to `Ready`, set priority)
+   - **Defer:** Move to backlog (Change status to `Deferred`, add reason)
+   - **Reject:** Archive (Change status to `Archived`, add reason)
+   - **Duplicate:** Merge with existing (Archive one, update other)
+
+3. **Validation Command:**
+   ```bash
+   # Update status in file
+   sed -i '' 's/Status: Pending/Status: Ready/' todos/{filename}
+   # OR
+   sed -i '' 's/Status: Pending/Status: Deferred/' todos/{filename}
+   ```
+
+---
+
+### Step 3: Hard Stop
+
+When time limit is reached:
+1. Stop processing
+2. Count remaining items
+3. Schedule next sprint if > 10 remain
+
+---
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Triage Sprint",
+  TaskStatus: "Sprint complete. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Processed X items. Y remain pending. Z moved to Ready."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Sprint complete
+
+Next steps:
+1. /work - Start working on items marked Ready
+2. /housekeeping - Archive rejected items
+```

package/skills/workflows/triage.md

@@ -1,152 +1,152 @@
----
-description: Triage and prioritize findings from code reviews. Use after /review to decide which issues to tackle.
----
-
-# /triage - Decision Workflow for Findings
-
-Go through findings one by one and decide whether to create todo items for them.
-
-> **Important:** Do NOT code during triage. This is for decision-making only.
-
-## When To Use
-
-- After `/review` generates findings
-- When processing security audit results
-- When reviewing performance analysis
-- For any list of issues needing prioritization
-
----
-
-## Workflow
-
-### Step 0: Search & Log
-
-```bash
-// turbo
-Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/triage", outcome: "success" }
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "prioritization"] }
-```
-
-### Step 0.1: Search Related Solutions
-
-Before approving a finding into a "ready" todo, check if this issue was already addressed in a different pattern or solution.
-
-```bash
-// turbo
-Call MCP `call_tool_compound_manager` { action: "search", terms: [ "{finding keywords}"] }
-```
-
----
-
-### Step 1: Load Pending Items
-
-```bash
-# List pending todos
-ls todos/*-pending-*.md 2>/dev/null || echo "No pending items"
-```
-
-### Step 2: Present Each Finding
-
-For each item, present:
-
-```
----
-Issue #{N}: {Brief Title}
-
-Severity: 🔴 P1 (CRITICAL) / 🟡 P2 (IMPORTANT) / 🔵 P3 (NICE-TO-HAVE)
-
-Category: {Security/Performance/Architecture/Bug/Feature}
-
-Description:
-{What's wrong or could be improved}
-
-Location: {file_path:line_number}
-
-Proposed Solution:
-{How to fix it}
-
-Estimated Effort: {Small <2h / Medium 2-8h / Large >8h}
-
----
-Decision?
-1. yes - Approve and mark as ready
-2. next - Skip this item (delete todo)
-3. custom - Modify before approving
-```
-
-### Step 3: Handle Decisions
-
-**When "yes":**
-1. Rename file: `{id}-pending-{pri}-{desc}.md` → `{id}-ready-{pri}-{desc}.md`
-2. Update YAML: `status: pending` → `status: ready`
-3. Confirm: "✅ Approved: Issue #{id} - Ready to work on"
-
-**When "next":**
-1. Delete the todo file
-2. Skip to next item
-3. Track as skipped for summary
-
-**When "custom":**
-1. Ask what to modify
-2. Update the information
-3. Present revised version
-4. Ask again
-
-### Step 4: Track Progress
-
-Show progress during triage:
-```
-Progress: 3/10 completed | ~2 minutes remaining
-```
-
-### Step 5: Final Summary
-
-```markdown
-## Triage Complete
-
-**Total Items:** {X}
-**Approved (ready):** {Y}
-**Skipped:** {Z}
-
-### Approved (Ready for Work):
-- `042-ready-p1-transaction-fix.md`
-- `043-ready-p2-cache-optimization.md`
-
-### Skipped:
-- Item #5: Low priority, defer to next sprint
-- Item #12: Not reproducible
-
-### Next Steps:
-1. Work on approved items: `/work todos/042-ready-p1-*.md`
-2. View ready todos: `ls todos/*-ready-*.md`
-```
-
-### Phase 5: Completion & Handoff
-
-#### Step 1: Establish Terminal UI State
-
-```javascript
-await task_boundary({
-  TaskName: "[COMPLETED] Triage Findings",
-  TaskStatus: "Findings prioritized. Offering next steps.",
-  Mode: "VERIFICATION",
-  TaskSummary: "Triaged {total} items. Approved: {ready}, Skipped: {skipped}."
-});
-```
-
-#### Step 2: Mandatory Handoff
-
-```bash
-✓ Triage complete
-
-Next steps:
-1. /work - Start working on approved items
-2. /resolve_todo - Batch process approved items
-```
-
----
-
-## References
-
-- Todos created by: `/review`, `/plan`, `/compound`
-- Work on todos: `/work`, `/resolve_todo`
+---
+description: Triage and prioritize findings from code reviews. Use after /review to decide which issues to tackle.
+---
+
+# /triage - Decision Workflow for Findings
+
+Go through findings one by one and decide whether to create todo items for them.
+
+> **Important:** Do NOT code during triage. This is for decision-making only.
+
+## When To Use
+
+- After `/review` generates findings
+- When processing security audit results
+- When reviewing performance analysis
+- For any list of issues needing prioritization
+
+---
+
+## Workflow
+
+### Step 0: Search & Log
+
+```bash
+// turbo
+Call MCP `call_tool_logger_manager` { action: "logWorkflow", name: "/triage", outcome: "success" }
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "prioritization"] }
+```
+
+### Step 0.1: Search Related Solutions
+
+Before approving a finding into a "ready" todo, check if this issue was already addressed in a different pattern or solution.
+
+```bash
+// turbo
+Call MCP `call_tool_compound_manager` { action: "search", terms: [ "{finding keywords}"] }
+```
+
+---
+
+### Step 1: Load Pending Items
+
+```bash
+# List pending todos
+ls todos/*-pending-*.md 2>/dev/null || echo "No pending items"
+```
+
+### Step 2: Present Each Finding
+
+For each item, present:
+
+```
+---
+Issue #{N}: {Brief Title}
+
+Severity: 🔴 P1 (CRITICAL) / 🟡 P2 (IMPORTANT) / 🔵 P3 (NICE-TO-HAVE)
+
+Category: {Security/Performance/Architecture/Bug/Feature}
+
+Description:
+{What's wrong or could be improved}
+
+Location: {file_path:line_number}
+
+Proposed Solution:
+{How to fix it}
+
+Estimated Effort: {Small <2h / Medium 2-8h / Large >8h}
+
+---
+Decision?
+1. yes - Approve and mark as ready
+2. next - Skip this item (delete todo)
+3. custom - Modify before approving
+```
+
+### Step 3: Handle Decisions
+
+**When "yes":**
+1. Rename file: `{id}-pending-{pri}-{desc}.md` → `{id}-ready-{pri}-{desc}.md`
+2. Update YAML: `status: pending` → `status: ready`
+3. Confirm: "✅ Approved: Issue #{id} - Ready to work on"
+
+**When "next":**
+1. Delete the todo file
+2. Skip to next item
+3. Track as skipped for summary
+
+**When "custom":**
+1. Ask what to modify
+2. Update the information
+3. Present revised version
+4. Ask again
+
+### Step 4: Track Progress
+
+Show progress during triage:
+```
+Progress: 3/10 completed | ~2 minutes remaining
+```
+
+### Step 5: Final Summary
+
+```markdown
+## Triage Complete
+
+**Total Items:** {X}
+**Approved (ready):** {Y}
+**Skipped:** {Z}
+
+### Approved (Ready for Work):
+- `042-ready-p1-transaction-fix.md`
+- `043-ready-p2-cache-optimization.md`
+
+### Skipped:
+- Item #5: Low priority, defer to next sprint
+- Item #12: Not reproducible
+
+### Next Steps:
+1. Work on approved items: `/work todos/042-ready-p1-*.md`
+2. View ready todos: `ls todos/*-ready-*.md`
+```
+
+### Phase 5: Completion & Handoff
+
+#### Step 1: Establish Terminal UI State
+
+```javascript
+await task_boundary({
+  TaskName: "[COMPLETED] Triage Findings",
+  TaskStatus: "Findings prioritized. Offering next steps.",
+  Mode: "VERIFICATION",
+  TaskSummary: "Triaged {total} items. Approved: {ready}, Skipped: {skipped}."
+});
+```
+
+#### Step 2: Mandatory Handoff
+
+```bash
+✓ Triage complete
+
+Next steps:
+1. /work - Start working on approved items
+2. /resolve_todo - Batch process approved items
+```
+
+---
+
+## References
+
+- Todos created by: `/review`, `/plan`, `/compound`
+- Work on todos: `/work`, `/resolve_todo`