hashgraph-online/awesome-codex-plugins / plugins/AgiFlow/ai-plugin/skills/backlog-grooming
backlog-grooming
UnverifiedReview Agiflow Planning tasks for readiness, prioritize approved work, group related tasks into work units, and promote ready tasks to Todo. Use when grooming a backlog, organizing planned tasks, creating work units, or deciding what should be executed next.
Agiflow Backlog Grooming
Treat grooming as the quality gate between Planning and Todo.
Workflow
- Resolve the target project and call
list_project_statusesto discover its exact status names. - Call
list_tasksfor Planning tasks,list_work_unitsfor existing active work units, andlist_membersfor assignment context. - Call
get_taskfor 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_unitsfor approved groups. - Use
update_taskto move only ready, ungated tasks to the exact Todo status and set their ordering.
- Use
- Verify with
list_tasksandlist_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-taskfor tasks that fail readiness checks.
Response
Report promoted tasks, created work units, items left in Planning, dependency gates, and the recommended execution order.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 107k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 107k | Updated | Claude CodeCodex | Verified | Install |