Review Agiflow Planning tasks for readiness, prioritize approved work, group related tasks into work units, and promote ready tasks to Todo.
SkillScore87Maintained
Automatic
◆Project Management pack
Last verified 8/15/2026
What it changes
Passed 17 of 20 test cases with the skill, and 10 of 20 without it.
Without skill48%
With skill87%
Checks it passed that the model alone missed
Specifies updating approved ready tasks to Todo status.
Explains trade-offs associated with the proposed priority order.
Includes remaining Planning tasks in the final report structure.
and 9 more in the full report
10 fixed10 passed either way2 still failing1 broke
Pass-rate lift
+39 pp
Tokens
-22%
Agent turns
0%
Response time
-44%
Model gemini-3.6-flashMeasured 8/15/2026v120 of 23 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
After executing the approved status updates and work unit creations for the 'Search Service' project, what final tool step is required to confirm success?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies calling list_tasks and list_work_units to verify the updated state.
Missed
Passed
case-15 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md35 linessingle file
Agiflow Backlog Grooming
Treat grooming as the quality gate between Planning and Todo.
Workflow
Resolve the target project and call list_project_statuses to discover its exact status names.
Call list_tasks for Planning tasks, list_work_units for existing active work units, and list_members for assignment context.
Call get_task for tasks whose readiness, dependencies, or acceptance criteria are unclear.
Classify every Planning task as:
Ready
Needs refinement
Blocked by a dependency
Duplicate or obsolete
Require a clear outcome, sufficient context, and at least two testable acceptance criteria before promotion.
Propose a priority order and explain the tradeoffs.
Group three to eight cohesive tasks into a work unit only when they deliver one shared capability. Leave one or two related tasks standalone and split groups larger than eight.
Review existing work units for shared dependencies and sequencing conflicts.
Present the proposed promotions, work units, assignments, and dependency order. Request approval before writing.
After approval:
Use batch_create_work_units for approved groups.
Use update_task to move only ready, ungated tasks to the exact Todo status and set their ordering.
Verify with list_tasks and list_work_units.
Guardrails
Never promote a vague task or a task missing testable acceptance criteria.
Never promote a downstream task whose required upstream work is incomplete.
Do not force unrelated work into one work unit.
Do not modify records before the user approves the proposed grooming plan.
Recommend refine-task for tasks that fail readiness checks.
Response
Report promoted tasks, created work units, items left in Planning, dependency gates, and the recommended execution order.