← AgiflowCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Agiflow
Snapshot Sep 30, 2026 · 22:51 UTC · version 3.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "daily-standup",
"description": "Produce a concise read-only Agiflow status summary covering completed work, work in progress, blockers, and recommended next priorities. Use for daily standups, morning checks, stakeholder updates, or a quick project pulse.",
"included_files": [],
"skill_md_contents": "---\nname: daily-standup\ndescription: Produce a concise read-only Agiflow status summary covering completed work, work in progress, blockers, and recommended next priorities. Use for daily standups, morning checks, stakeholder updates, or a quick project pulse.\n---\n\n# Agiflow Daily Standup\n\nGive a brief, evidence-based project pulse. Do not modify workspace data.\n\n## Workflow\n\n1. Call `get_current_scope` and resolve the requested project when needed.\n2. Call `list_active_tasks_by_org` for current active work.\n3. Call `list_work_units` for active and blocked work units.\n4. Call `get_project_detail` when the summary is project-specific.\n5. Call `list_members` to resolve assignee context.\n6. Call `get_task`, `get_work_unit_progress`, or `list_task_comments` only when needed to confirm progress or a blocker.\n7. Summarize:\n - Done or moved to Review since the latest available update\n - Current work in progress\n - Blocked or stalled items\n - Highest-priority next actions\n\n## Priority Logic\n\n1. Resolve blockers that prevent other work.\n2. Finish existing work in progress before starting more work.\n3. Select the highest-priority ready item.\n4. Recommend refinement when a task is not ready.\n\n## Output Format\n\nUse short sections titled Done, In Progress, Blocked, and Next Up. Include task or work-unit identifiers when available. State clearly when no recent changes or blockers are found.\n\n## Guardrails\n\n- Remain read-only. Do not call mutation tools.\n- Do not claim an item changed recently unless the returned data supports that conclusion.\n- Distinguish confirmed blockers from possible signs of stalled work.\n- Keep the summary scannable and end with one clear recommendation.\n"
}SHA-256: 61af96374208ea930c7d61414fc44e46b345da7a1db50d19f78b801e33c745cb