Forge-Backlog-Refinement

Refines, decomposes, and de-duplicates backlog work items into execution-ready sets.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-backlog-refinement-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Backlog-Refinement
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/01-Product/Forge-Backlog-Refinement
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-backlog-refinement-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlogs decay into vague wish-lists or duplicate graveyards when left unrefined, forcing teams to re-litigate intent before every iteration. This Skill keeps the top of the backlog execution-ready by decomposing oversized items, consolidating duplicates, and verifying readiness before iteration planning. ## Core Features & Use Cases - Backlog Triage & De-duplication: Sweep the backlog for stale, duplicated, or superseded items and consolidate or retire them with documented rationale. - Decomposition & Detailing: Split oversized items into deliverable work items with traceability from parent to children, confirming intent, boundaries, and dependencies. - Readiness Verification & Cohort Sizing: Check scope alignment, terminology, and acceptance-criteria presence, then apply cohort-level sizing suitable for sequencing without false precision. - Use Case: Before sprint planning, run refinement across the backlog so the AI Program Manager and Product Owner hand Forge-Task-Routing a clean, execution-ready set of work items with current metadata. ## Quick Start Review the current backlog, decompose any oversized work items, consolidate duplicates, and flag which items are execution-ready for the next iteration.

Frequently Asked Questions about Forge-Backlog-Refinement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep a product backlog ready for sprint planning?▼

Run continuous backlog refinement: triage stale or duplicate items, decompose oversized items into deliverable work items, verify acceptance criteria and dependencies, then flag execution-ready items. This keeps the top of the backlog consumable without re-clarification sessions.

What is the difference between backlog refinement and prioritisation?▼

Prioritisation decides the relative value and order of work items, while refinement owns readiness: clarity, decomposition, de-duplication, and sizing. Refinement never reorders items by value; it only ensures ordered items are executable.

How do I handle duplicate backlog items?▼

Sweep the backlog comparing items against completed-item history and active items, then consolidate or retire duplicates with documented rationale. Preserving traceability from parent to child items prevents losing context during consolidation.

When should I not use backlog refinement?▼

Do not use refinement to decide what is worth doing (that is prioritisation), to define acceptance criteria from scratch, or to reshape project direction. Refinement only verifies readiness of items whose value and intent are already established.

How granular should backlog item estimates be?▼

Apply cohort-level sizing: fine-grained enough to support sequencing decisions, but coarse enough to avoid false precision. Near-term items get detailed refinement while distant items stay intentionally coarse.