skills.rest
ThanabordeeN
ThanabordeeNCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

product-backlog-agent

Convert user requirements into backlog, user stories, and sprint plan files.

Updated Mar 5, 2026
Search Tags:#automation#documentation#backlog#sprint#project-management#user-stories#moscow
One-click install
npx skills add https://github.com/ThanabordeeN/gemini-productivity-skills --skill product-backlog-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-backlog-agent
Source: https://github.com/ThanabordeeN/gemini-productivity-skills/tree/main/product-backlog-agent
Command: npx skills add https://github.com/ThanabordeeN/gemini-productivity-skills --skill product-backlog-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to translate raw requirements into a structured backlog and actionable sprint plan, causing misalignment and bottlenecks in delivery.

Core Features & Use Cases

  • Convert requirements into a structured backlog (Epics, Features, and User Stories) ready for planning.
  • Generate user stories with acceptance criteria from a feature list and prioritize via MoSCoW.
  • Plan sprints, assign tasks to developers, and produce sprint planning artifacts (xlsx and docx) for execution.

Quick Start

Ask me to convert your project requirements into a complete backlog, user stories, and sprint plan.

Frequently Asked Questions about product-backlog-agent

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

FAQPage Schema
How do I convert raw project requirements into a structured product backlog?▼

To convert raw project requirements into a product backlog, you provide the inputs to generate Epics, Features, and User Stories. This structures your needs into a formatted backlog Excel file ready for planning.

Can I generate user stories with MoSCoW prioritization and story points automatically?▼

Yes, you can generate user stories complete with acceptance criteria, MoSCoW priorities, and story points automatically. The skill reads your requirements and outputs a structured Word document containing the documented stories.

How do I plan sprints and assign tasks to developers from a feature list?▼

Sprint planning and task assignment are handled by processing your feature list to allocate stories into sprints. It produces a sprint plan Excel file that details task statuses and developer assignees for execution.

Do I need to format my requirements in a specific template before generating a backlog?▼

No specific input template is required as the skill reads user inputs or uploaded requirements directly. It handles the formatting internally to ensure the output backlog and sprint plans use the correct Excel and Docx structures.

What is the best way to automate sprint planning and user story documentation?▼

Automating sprint planning and user story documentation is best done by feeding requirements into a single processing workflow. This coordinates backlog generation, story documentation, and sprint-task allocation to produce ready-to-use planning packages.

Why does translating requirements into a backlog cause delivery bottlenecks?▼

Translating requirements into a backlog causes bottlenecks when teams fail to structure raw needs into actionable Epics and User Stories. This misalignment prevents effective sprint planning and slows down development execution.

Related Skills

Explore More Product & Management Skills→
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced
MazenMradMazenMrad
1

gds-sprint-status

Summarize sprint status and surface risks from sprint-status.yaml.

Community
Advanced
abhilash-nandkumarabhilash-nandkumar

user-story-fundamentals

Capture user requirements into structured user stories with acceptance criteria.

Community
Intermediate
Emz1998Emz1998
1

reporting-sprints

Generate sprint reports with goals, completed work, blockers, and velocity.

Community
Basic