Individual skill

triage

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.

plugins/AgiFlow/ai-plugin/skills/triage/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,533
Repository last updated: Nov 6, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-coding Repository topic
awesome Repository topic
awesome-list Repository topic
codex Repository topic
codex-plugins Repository topic
openai Repository topic
codex-skill Repository topic
codex-skills Repository topic
marketplace Repository topic
codex-marketplace Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,910 bytes

Read excerpt


# Agiflow Triage

Diagnose before prescribing. Read the workspace first and separate evidence from inference.

## Workflow

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