Skills Guide

Gestion du Backlog Produit

VérifiéSûr

Crée et maintient un fichier de backlog produit structuré (backlog.md) contenant des épopées, user stories, stories techniques, bugs et spikes. Permet d'organiser les éléments de travail du projet, de définir les priorités (Must have, Should have, Nice to have) et de suivre l'avancement tout au long du développement. Idéal pour la planification de sprint et la gestion de projet.

Spar Skills Guide Bot
DeveloppementIntermédiaire
6002/06/2026
Claude CodeCursorWindsurfCopilotCodex
#backlog#product-management#agile#sprint-planning#epic

Recommandé pour

Développeur backendClaude CodeRevue de codeCursorDéveloppeur frontendCopilot

Notre avis

Crée et gère un fichier backlog.md structuré avec epics, user stories, technical stories, bugs et spikes pour le suivi de projet.

Points forts

  • Structure claire et cohérente grâce à un template prédéfini
  • Gestion des priorités (Must have, Should have, Nice to have) et des dépendances
  • Suivi des bugs et des spikes avec référence aux stories
  • Mise à jour automatique des statuts et des compteurs

Limites

  • Nécessite un template spécifique pour fonctionner correctement
  • Ne gère pas la granularité des tâches (celles-ci sont réservées au sprint planning)
  • Dépend de la lecture de plusieurs fichiers de specs pour le contexte
Quand l'utiliser

Lorsque vous démarrez un nouveau projet ou que vous devez structurer et prioriser un backlog produit de manière standardisée.

Quand l'éviter

Pour des projets très agiles avec des backlogs légers ou quand vous utilisez un outil externe de gestion de projet (Jira, Trello, etc.) comme source unique.

Analyse de sécurité

Sûr
Score qualité88/100

The skill reads project files and writes to a backlog markdown file. It does not execute any destructive commands, network access, or handle sensitive data beyond file operations. No obfuscation or exfiltration risk is present.

Aucun point d'attention détecté

Exemples

Create a new product backlog
Create a product backlog for our new social media app based on the product brief and architecture docs.
Add an epic to the backlog
Add an epic called 'User Authentication' with priority 'Must have' and three user stories: login, registration, and password reset.
Move completed stories to done
Update the backlog: move all stories with status 'Done' from the epic 'User Profile' to the Completed section.

name: backlog description: Creates and manages product backlog markdown files with epics, user stories, technical stories, bugs, and spikes. Use when creating backlogs, adding epics/stories/tasks, updating story status, or when user mentions backlog, sprint planning, project management, or task tracking.

Goal: Create and maintain a structured backlog.md file at project/workflow/backlog.md using the template at template/backlog.md.

Instructions

  • Read project specs for context before creating or modifying the backlog
  • Hierarchy: Epics (EP-NNN) contain stories (US-NNN, TS-NNN, BG-NNN, SK-NNN). Tasks (T-NNN) are created at sprint level, not in the backlog
  • All IDs are global and sequential within their prefix
  • Use priority levels: Must have, Should have, Nice to have
  • Spikes reference which story they unblock
  • Bugs reference the story they were found in (if known)
  • A story can only belong to one epic
  • Stories that don't fit an epic go in Tech Debt / Infrastructure or Bug Backlog sections

Workflow

  1. Read project specs for context:

    • Product Brief: project/docs/product/product-brief.md
    • Architecture: project/docs/architecture/architecture.md
    • Coding Standards: project/docs/architecture/coding-standards.md
    • Definition of Done: project/docs/governance/definition-of-done.md
    • Decisions: project/docs/architecture/decisions.md

  2. Read the backlog template: template/backlog.md

  3. Check if backlog.md exists at project/workflow/backlog.md. If not, create it from the template.

  4. Create or update the backlog following the template structure:

    • Fill the Epics Overview table with all epics and their priorities
    • Fill Epic Details sections with stories for each epic
    • Populate Tech Debt / Infrastructure and Bug Backlog as needed
    • Move completed stories to the Completed table

  5. Provide summary report to the user

Rules

  • Most stories should be independent per INVEST principles
  • Avoid dependencies between stories as much as possible
  • Do not add task-level detail to the backlog; that belongs in sprint planning
  • Must have bugs take priority over Should have stories in the next sprint
  • Reprioritize at every sprint close based on Scrum Master recommendations
  • Stories use their type-specific format (US/TS/BG/SK) matching sprint.md conventions

Acceptance Criteria

  • Backlog follows the exact structure from template/backlog.md
  • All IDs follow correct patterns (EP-NNN, US-NNN, TS-NNN, BG-NNN, SK-NNN)
  • Each epic has a description, priority, and status
  • Stories use the correct format: "As a [user], I want [what] so that [why]"
  • Priority legend, status values, and ID conventions match the template
  • Epics Overview table accurately reflects current counts and statuses
  • File written to correct path: project/workflow/backlog.md
Skills similaires

Expert Next.js App Router

Developpement

Un skill qui transforme Claude en expert Next.js App Router.

Claude CodeCursoradvanced
890
234
2,846
Admin

Générateur de README

Developpement

Crée des README.md professionnels et complets pour vos projets.

claudeCursorWindsurfbeginner
259
72
821
Admin

Rédacteur de Documentation API

Developpement

Génère de la documentation API complète au format OpenAPI/Swagger.

claudeCursorWindsurfintermediate
156
44
682
Admin