Backlog Creation

Backlog Creation

Create and structure the initial product backlog for "$ARGUMENTS". Break roadmap themes into epics and user stories, prioritize using MoSCoW or WSJF, identify MVP scope, and tag stories with labels.

Prerequisites

Check that .project/$ARGUMENTS/00-initiate.md exists. If it does not, tell the user to run an Initiate skill first (e.g., project-charter) and stop.

If the user passes --skip-checks, skip the prerequisite check and log the skip to .project/$ARGUMENTS/skip-log.md with a timestamp and reason.

Process

1. Read existing context:

   • Read .project/$ARGUMENTS/00-initiate.md for charter and scope context
   • Read .project/$ARGUMENTS/01-plan.md if it exists (for vision, goals, and roadmap)
   • Read plugins/project-management/shared/user-story-template.md for story format
   • Read plugins/project-management/shared/scrum-guide.md for Scrum alignment

2. Break roadmap themes into epics:

   • For each theme from the roadmap, identify constituent epics
   • For each epic: name, description, acceptance criteria, estimated size (S/M/L/XL)
   • Ensure epics are large enough to be meaningful but small enough to complete in 1-3 sprints
   • If no roadmap exists yet, derive epics directly from charter scope and objectives

3. Break epics into user stories:

   • Write each story in "As a [persona], I want [action], so that [benefit]" format
   • Aim for 3-8 stories per epic (split epics that generate more than 10 stories)
   • Ensure each story delivers value independently where possible
   • Add brief acceptance criteria to each story (detailed criteria come in the user-stories skill)

4. Prioritize the backlog:

   • Select a prioritization method:
     • MoSCoW: Must have, Should have, Could have, Won't have (this time)
     • WSJF (Weighted Shortest Job First): (Business Value + Time Criticality + Risk Reduction) / Job Size
   • Apply the method consistently across all stories
   • Document the rationale for high-priority and deprioritized items
   • Resolve priority conflicts by referencing product goals and North Star metric

5. Structure the backlog by priority:

   • Order stories from highest to lowest priority
   • Group by epic for readability, but maintain priority order within each epic
   • Number stories for easy reference (e.g., EPIC-001, EPIC-002)
   • Include a priority summary showing the distribution (how many Must/Should/Could/Won't)

6. Identify MVP scope:

   • MVP = all Must-have stories (or highest-WSJF stories that fit within first milestone)
   • Validate that MVP delivers a coherent, usable product — not just a random subset
   • Check that MVP aligns with the first release milestone from the roadmap
   • Flag any Must-have stories that feel too large or risky for MVP

7. Tag stories with labels:

   • Type: feature, bug, tech-debt, spike (research), infrastructure
   • Component: frontend, backend, API, database, DevOps, design
   • Risk level: high, medium, low
   • Ensure labels are consistent and will be useful for filtering and reporting

8. Write the artifact — append to .project/$ARGUMENTS/01-plan.md under a ## Product Backlog section:

   • Epics Summary — list of epics with size, theme, and story count
   • Prioritized Backlog — ordered list of stories with priority, epic, labels
   • MVP Scope — stories included in MVP with rationale
   • Priority Distribution — counts by MoSCoW category or WSJF bands
   • Label Summary — counts by type and component labels

Output

Product backlog appended to .project/$ARGUMENTS/01-plan.md. Present a summary highlighting:

• Total number of epics and stories created
• MVP scope: number of stories and estimated effort
• Priority distribution across MoSCoW categories
• Any gaps or risks identified during backlog creation