hashgraph-online/awesome-codex-plugins / plugins/AgiFlow/ai-plugin/skills/backlog-grooming
backlog-grooming
VerifiedReview 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.1 KB |
SKILL.md
View on GitHub---
name: backlog-grooming
description: Review 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
1. Resolve the target project and call `list_project_statuses` to discover its exact status names.
2. Call `list_tasks` for Planning tasks, `list_work_units` for existing active work units, and `list_members` for assignment context.
3. Call `get_task` for tasks whose readiness, dependencies, or acceptance criteria are unclear.
4. Classify every Planning task as:
- Ready
- Needs refinement
- Blocked by a dependency
- Duplicate or obsolete
5. Require a clear outcome, sufficient context, and at least two testable acceptance criteria before promotion.
6. Propose a priority order and explain the tradeoffs.
7. 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.
8. Review existing work units for shared dependencies and sequencing conflicts.
9. Present the proposed promotions, work units, assignments, and dependency order. Request approval before writing.
10. 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.
11. 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.
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: 119k | 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: 118k | Updated | Claude CodeCodex | Verified | 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: 108k | 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: 108k | Updated | Claude CodeCodex | Verified | Install |