backlog

Generates prioritized product backlog items with acceptance criteria from slice discovery documents.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill backlog-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/backlog
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill backlog-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning high-level slice discovery documents into concrete, estimable user stories is time-consuming and often produces stories that lose traceability to their source scope. This Skill automates the creation of Product Backlog Items (PBIs) that stay traceable to slices and follow a consistent format. ## Core Features & Use Cases - Slice-Traceable Story Generation: Reads each docs/05_scrum/discovery/S#.md file and generates 3-7 user stories per slice, each referencing its source slice. - Structured Story Format: Produces stories with persona-based phrasing, acceptance criteria checklists, story point estimates (1/2/3/5/8), and MoSCoW priorities. - Prioritization and Summary: Supports MoSCoW, slice-order, or business-value prioritization and writes a summary table to docs/05_scrum/backlog.md. - Use Case: After completing slice discovery for S1 and S2, run this Skill to produce a ready-to-refine backlog where every story links back to its slice and includes acceptance criteria aligned with your definition of ready. ## Quick Start Ask the assistant to generate the product backlog from the slice discovery documents in docs/05_scrum/discovery and write it to docs/05_scrum/backlog.md.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I generate a product backlog from slice discovery documents?▼

Run the backlog skill after completing at least one slice discovery document in docs/05_scrum/discovery. It scans the S#.md files, generates 3-7 user stories per slice with acceptance criteria and story points, and writes the result to docs/05_scrum/backlog.md.

What format do the generated user stories follow?▼

Each story uses the format 'As a [persona], I want [action], so that [outcome]' followed by acceptance criteria checkboxes, story points (1/2/3/5/8), a MoSCoW priority, and the source slice reference. Personas come from docs/01_product/04_personas.md.

What happens if no slice discovery documents exist?▼

The skill stops and reports that no slice files were found in docs/05_scrum/discovery. It then offers to invoke the slices-discovery skill first, since backlog generation requires at least one completed slice.

Can I generate backlog items for only specific slices?▼

Yes. During execution the skill asks which slices to include: all slices, a single slice, or a specific selection by name. Stories are then generated only for the chosen slices.

What are the limitations of the generated story estimates?▼

Story points follow a fixed guide from 1 (trivial) to 8 (too big). Any story estimated at 8 points is flagged as too large and should be split before sprint planning. Estimates are suggestions that the user reviews and adjusts before writing.