Update to Agiflow

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -3,37 +3,87 @@
 description: Diagnose stalled, blocked, overloaded, or unhealthy Agiflow projects and recommend specific corrective actions. Use for project health checks, blocked work, conflicting priorities, obsolete tasks, overloaded assignees, or an unmanageable backlog.
 ---
 
-# Agiflow Triage
+# Triage
 
-Diagnose before prescribing. Read the workspace first and separate evidence from inference.
+Find out why a project is stuck and recommend specific actions. Diagnose first, then let the user decide what to change.
 
-## Workflow
+## Guardrails
 
-1. Call `get_current_scope` and resolve the target project when one is specified.
-2. Call `list_active_tasks_by_org`, `list_work_units`, and `list_members`.
-3. For relevant items, call `get_task`, `get_work_unit`, `get_work_unit_progress`, and `list_task_comments` to inspect details and documented blockers.
-4. Identify:
-   - Stalled tasks or work units
-   - Explicit blockers and unresolved dependencies
-   - Missing or vague acceptance criteria
-   - High-priority unassigned work
-   - Excessive work in progress
-   - Obsolete or duplicate tasks
-   - Priority inversions
-5. Classify each finding as Blocker, Warning, or Note.
-6. Recommend one specific action for each finding and explain the expected impact.
-7. Present the report and ask which actions the user approves.
-8. Execute only approved actions with the appropriate tools, such as `update_task`, `create_task`, `batch_create_tasks`, or `create_task_comment`.
-9. Re-read affected records to verify the result.
-
-## Mutation Rules
-
-- Do not change anything during diagnosis.
-- Document the reason with `create_task_comment` before cancelling or materially re-scoping a task.
-- Use `update_task` only after approval for reassignment, priority, status, or scope changes.
-- Create new tasks only when the user approves the proposed corrective work.
-- Do not use deletion as a default cleanup action.
+- Diagnose before prescribing.
+- Report by severity: blockers, then warnings, then notes.
+- Recommend one specific action per problem (reassign, split, refine, cancel, re-prioritize), not vague advice.
+- Make no changes until the user approves specific actions.
+- Before cancelling a task, record the reason with `create_task_comment`.
 
-## Response
+## 1. Load project state
 
-Provide a concise health summary, evidence for each finding, severity, recommended action, and the three highest-priority next steps.
+1. `list_active_tasks_by_org` for all active work, or `list_tasks` with `statusFilter: "active"` for one project.
+2. `list_tasks` with `view: "attention"` for the shared queue of blocked, overdue, in-review, rejected, and stale items.
+3. `list_work_units` and `get_work_unit_progress` for work-unit health.
+4. `list_members` for capacity.
+5. `get_project_detail` and `list_project_statuses` when a project is named.
+6. For stalled or blocked items, read `list_task_comments` and `get_task` to learn why.
+
+## 2. Identify problems
+
+- **Stalled**: in progress with no recent movement; work units whose tasks have not moved; assigned but inactive work.
+- **Blocked**: blocked work units or tasks, blocker comments with no follow-up, work waiting on unfinished prerequisites.
+- **Quality gaps**: tasks without acceptance criteria or with vague descriptions; unassigned high-priority tasks; work units with more than eight tasks.
+- **Imbalance**: one assignee with many in-progress tasks; everything in progress and nothing done; high-priority work waiting while low-priority work is active.
+
+Do not infer how long something has waited from `updatedAt` alone; say when timing is unknown.
+
+## 3. Classify severity
+
+| Severity | Meaning | Action |
+| --- | --- | --- |
+| **BLOCKER** | Stops progress on the critical path | Resolve now |
+| **WARNING** | Creates risk or waste | Resolve soon |
+| **NOTE** | Improvement opportunity | When convenient |
+
+## 4. Recommend actions
+
+| Problem | Action | Tools |
+| --- | --- | --- |
+| Task too large and stalled | Split into smaller tasks | `batch_create_tasks`, then `update_task` on the original |
+| Unclear scope or no acceptance criteria | Refine | Suggest `refine-task` |
+| Blocked by missing work | Create the unblocking task | `create_task` |
+| Assignee overloaded | Reassign | `update_task` |
+| No focus | Finish one work unit first | `update_task` priorities |
+| Wrong priorities | Re-prioritize | `update_task`, `reorder_tasks` |
+| Obsolete or descoped | Cancel with a documented reason | `create_task_comment`, then `update_task` |
+| Todo task needs re-scoping | Move back to Planning | `update_task` |
+| Urgent incoming bug | Create in Planning with a `bug:` tag and high priority | `create_task`, then suggest `backlog-grooming` |
+
+## 5. Present the report
+
+```
+## Triage Report
+Scope: [organization or project]   Date: [today]
+
+Summary: active [N], in progress [N], blocked [N]; [N] blockers, [N] warnings, [N] notes
+
+Blockers
+1. [task or work unit id]: [problem]
+   Recommendation: [action]. Impact if ignored: [effect]
+
+Warnings
+1. [id]: [problem]. Recommendation: [action]
+
+Notes
+1. [observation]: [suggestion]
+
+Health: Healthy / Needs attention / At risk
+Next steps: 1. ... 2. ... 3. ...
+```
+
+## 6. Act only with approval
+
+Ask which actions to take. Apply only the approved ones, then re-read the affected tasks or `list_active_tasks_by_org` to confirm the result.
+
+## Common mistakes
+
+- Reporting status without finding causes
+- Vague suggestions ("improve descriptions")
+- Changing data without approval
+- Ignoring blocked items or skipping their comments