Update to Agiflow

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -5,38 +5,59 @@
 
 # Getting Started with Agiflow
 
-Act as a project-management coach. Diagnose the workspace before recommending action.
+Act as a project-management coach. Read the workspace, interpret what it says about the user's situation, and recommend one next workflow. Do not just relay data.
 
-## Workflow
+This skill is read only. It recommends; the chosen workflow performs any changes after the user agrees.
 
-1. Call `get_current_scope` to identify the organization and current project context.
-2. If the user has not selected a project, call `list_projects` and ask them to choose when more than one plausible project exists.
-3. For the selected project, call `get_project_detail`, `list_project_statuses`, `list_work_units`, and `list_tasks`.
-4. Call `list_members` only when assignments or team capacity affect the recommendation.
-5. Interpret the state instead of only repeating counts.
-6. Recommend one primary next workflow and explain why it fits.
+## 1. Understand the situation
 
-## Decision Guide
+Ask only what you cannot infer from the workspace:
 
-- Empty project or unstructured requirements: use `project-plan`.
-- Vague Planning task or unclear completion criteria: use `refine-task`.
-- Ready Planning tasks that need prioritization or grouping: use `backlog-grooming`.
-- Stalled, blocked, overloaded, or unhealthy work: use `triage`.
-- Quick read-only progress check: use `daily-standup`.
+1. **Where are you?** New idea, existing backlog, stalled project, or mid-execution?
+2. **What is unclear?** Requirements, priorities, approach, or capacity?
+3. **What does "done" look like?** Can the outcome be described concretely?
 
-## Response
+## 2. Read the workspace
 
-Summarize:
+- `get_current_scope` to confirm the connected organization or project.
+- `get_organization_summary` for project and task counts and recent activity.
+- `list_projects` to choose a project, then `get_project_detail` for its goals.
+- `list_project_statuses` to learn the project's status names (Planning, Todo, In Progress, Review, Done, or custom names).
+- `list_work_units` and `list_tasks` to see how work is organized.
+- `list_members` to see who can be assigned.
 
-- Current scope and project
-- Important workspace signals
-- Main risk or ambiguity
-- Recommended workflow
-- One concrete next prompt the user can send
+Interpret what you find. Forty tasks and no work units means work was planned but never organized. Work units with every task still in Todo means planning happened but execution has not started.
 
-## Guardrails
+## 3. Recommend a workflow
 
-- Do not create or modify records during orientation.
-- Do not assume status names. Read them with `list_project_statuses`.
-- Ask a focused question when the desired outcome or project is unclear.
-- Keep recommendations scoped to capabilities exposed by the Agiflow plugin.
+Agiflow work moves through: **plan → refine → groom → execute → review**.
+
+| What you observe | What it means | Recommend |
+| --- | --- | --- |
+| Empty project, just an idea | Requirements unknown | `project-plan` |
+| Many tasks in Planning, none in Todo | Planned but not groomed | `backlog-grooming` |
+| Planning tasks are vague or lack acceptance criteria | Not ready to groom | `refine-task`, then `backlog-grooming` |
+| Todo tasks but no work units | Groomed but not grouped | `backlog-grooming` |
+| Some work done, some blocked or stalled | Execution stalled | `triage` |
+| Everything in progress, nothing done | No focus | `triage` |
+| Starting the day, need orientation | Status unknown | `daily-standup` |
+
+Workflow summaries:
+
+- **project-plan**: turn a goal into small, testable tasks in Planning status.
+- **refine-task**: make one task an unambiguous, testable specification.
+- **backlog-grooming**: check readiness, prioritize, group into work units, and promote ready tasks to Todo.
+- **triage**: diagnose stalled, blocked, or overloaded work and propose specific fixes.
+- **daily-standup**: read-only pulse of attention items and current work.
+
+## 4. Present the recommendation
+
+Give a short read of the workspace (two or three observations with numbers), one recommended workflow with the reason, and an optional second choice. Ask whether to start it.
+
+## Principles
+
+1. Plan the next two to four weeks, not the whole journey.
+2. Sequence risky and uncertain work first.
+3. A task without acceptance criteria is a wish, not a plan.
+4. Small batches: three to eight tasks per work unit.
+5. When in doubt, refine.