← AgiflowCONTENT HISTORY

Update to Agiflow

Snapshot Sep 30, 2026 · 22:51 UTC · version 3.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "getting-started",
  "description": "Assess an authenticated Agiflow workspace and recommend the right next project-management workflow. Use when a user is new to Agiflow, asks what to do next, needs orientation, or is unsure whether to plan, refine, groom, triage, or review daily status.",
  "included_files": [],
  "skill_md_contents": "---\nname: getting-started\ndescription: Assess an authenticated Agiflow workspace and recommend the right next project-management workflow. Use when a user is new to Agiflow, asks what to do next, needs orientation, or is unsure whether to plan, refine, groom, triage, or review daily status.\n---\n\n# Getting Started with Agiflow\n\nAct as a project-management coach. Diagnose the workspace before recommending action.\n\n## Workflow\n\n1. Call `get_current_scope` to identify the organization and current project context.\n2. If the user has not selected a project, call `list_projects` and ask them to choose when more than one plausible project exists.\n3. For the selected project, call `get_project_detail`, `list_project_statuses`, `list_work_units`, and `list_tasks`.\n4. Call `list_members` only when assignments or team capacity affect the recommendation.\n5. Interpret the state instead of only repeating counts.\n6. Recommend one primary next workflow and explain why it fits.\n\n## Decision Guide\n\n- Empty project or unstructured requirements: use `project-plan`.\n- Vague Planning task or unclear completion criteria: use `refine-task`.\n- Ready Planning tasks that need prioritization or grouping: use `backlog-grooming`.\n- Stalled, blocked, overloaded, or unhealthy work: use `triage`.\n- Quick read-only progress check: use `daily-standup`.\n\n## Response\n\nSummarize:\n\n- Current scope and project\n- Important workspace signals\n- Main risk or ambiguity\n- Recommended workflow\n- One concrete next prompt the user can send\n\n## Guardrails\n\n- Do not create or modify records during orientation.\n- Do not assume status names. Read them with `list_project_statuses`.\n- Ask a focused question when the desired outcome or project is unclear.\n- Keep recommendations scoped to capabilities exposed by the Agiflow plugin.\n"
}

SHA-256: 8fa64630144860d5759c628c2d7dc10ea9c5f1487d0f88011b700e387586b3aa