From agile-lifecycle
This skill should be used when shaping the product backlog, prioritizing stories, or preparing items for sprint readiness. Triggers when entering Phase 3 (Discovery), transitioning to Phase 4 (Delivery), or when backlog health needs assessment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agile-lifecycle:backlog-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The product backlog is the single source of truth for all work. This skill governs how backlog items are shaped, estimated, prioritized, and declared sprint-ready. It bridges the discovery output of Phase 3 into a delivery-ready backlog for Phase 4. A well-managed backlog reduces sprint planning friction, prevents scope creep, and maintains alignment between the Product Owner and the delivery t...
The product backlog is the single source of truth for all work. This skill governs how backlog items are shaped, estimated, prioritized, and declared sprint-ready. It bridges the discovery output of Phase 3 into a delivery-ready backlog for Phase 4. A well-managed backlog reduces sprint planning friction, prevents scope creep, and maintains alignment between the Product Owner and the delivery team.
Review existing backlog items and their current status. Load references/artefact-catalog.md to understand mandatory backlog artefacts for the current phase. If transitioning from Phase 3, check that discovery output artefacts are available as input.
For each feature or capability identified in Phase 3:
templates/phase-3/sprint-backlog.md.template to structure each itemid, title, epic (parent feature), user_story (As a / I want / So that), business_value, priorityFor each backlog item, define acceptance criteria using the format in templates/phase-3/acceptance-criteria.md.template:
skills/definition-of-done/SKILL.md)With the delivery team during refinement:
The Product Owner orders the backlog based on:
Apply MoSCoW or weighted shortest job first (WSJF) as the team's chosen prioritization method. Document the method chosen and rationale for top-of-backlog ordering.
Before an item enters sprint planning, it must be sprint-ready:
Items that do not meet readiness criteria stay in refinement — they do not enter the sprint backlog.
At the end of each sprint and before each gate review, assess backlog health:
templates/phase-3/sprint-backlog.md.template — Sprint backlog and backlog item structuretemplates/phase-3/acceptance-criteria.md.template — Acceptance criteria patternsreferences/artefact-catalog.md — Mandatory backlog artefacts by phaseschemas/sprint-contract.schema.jsonnpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin agile-lifecycleCreates and maintains product/project backlogs with prioritization, acceptance criteria, and estimates. Supports user stories, MoSCoW, grooming, and tracking.
Generates prioritized user stories with Given/When/Then acceptance criteria, story point estimates, and MoSCoW prioritization for sprint planning.
Prioritizes validated user stories using 5 weighted lenses, generates iterative batches with anti-waterfall rules. Triggered by phrases like 'prioritize stories' or 'order backlog'.