agile-project-manager

Generates user stories, sprint plans, backlog priorities, and retro action items for agile teams.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/rpmcdougall/claude-skills --skill agile-project-manager-rpmcdougall
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agile-project-manager
Source: https://github.com/rpmcdougall/claude-skills/tree/main/skills/agile-project-manager
Command: npx skills add https://github.com/rpmcdougall/claude-skills --skill agile-project-manager-rpmcdougall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to write testable user stories, plan realistic sprints, keep backlogs prioritized, and run retrospectives that produce actual change. This Skill applies a pragmatic agile project manager perspective to turn vague work requests into structured, deliverable plans. ## Core Features & Use Cases - Story & Task Writing: Produces user stories with mandatory value statements, testable acceptance criteria, technical notes, and explicit out-of-scope sections sized for 1-3 days of work. - Sprint Planning & Estimation: Clarifies sprint goals, checks team capacity at 70-80%, maps dependencies, flags risks, and gives ranged relative estimates instead of false-precision single points. - Backlog Grooming & Retros: Enforces strict stack ranking, kills zombie tickets, spots missing work (error handling, deploy, monitoring stories), and structures retros around concrete action items with owners and deadlines. - Use Case: A team lead pastes a feature idea and asks to break it down; the Skill returns tracker-ready stories with acceptance criteria, identifies dependencies, and proposes a committed versus stretch sprint scope. ## Quick Start Ask the assistant to break this feature into sprint-ready user stories with acceptance criteria and a prioritized backlog order.

Frequently Asked Questions about agile-project-manager

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

FAQPage Schema
How do I write a good user story with acceptance criteria?▼

A good user story follows the 'As a / I want / so that' format where the value clause is mandatory. Acceptance criteria must be observable and testable by someone who didn't write the code, such as a specific HTTP status and response body, not vague phrases like 'works correctly'.

How to break down a large feature into sprint tasks?▼

Split work so each story is deliverable by one person in 1-3 days; anything bigger gets decomposed further. Explicitly name what is out of scope for each story to prevent mid-sprint scope creep, and map dependencies so blocking items are scheduled first.

What is the best way to estimate software work?▼

Use relative sizing against known past work rather than absolute time estimates, and never give a single-point number. Provide a range tied to assumptions, such as '2-3 days if the existing auth middleware works, 5-7 if it needs modification', and timebox unknowns as research spikes.

How do I prioritize a backlog with too many high-priority items?▼

Replace high/medium/low buckets with a strict stack rank where every item has a unique position. Flag tickets idle for 3+ months as zombies for closure or refinement, and check for gaps like missing error-handling, frontend, deploy, or monitoring stories.

Does this skill require a specific agile framework like Scrum?▼

No, it adapts to whatever process the team already uses, whether Scrum, Kanban, or Shape Up. It treats frameworks as tools rather than doctrine and never prescribes a specific methodology unless the user asks for one.

Why do sprint retrospectives fail to produce change?▼

Retros fail when action items are vague, like 'communicate better', instead of concrete commitments with an owner and deadline. Limit outcomes to one or two items, review last retro's actions first, and focus on systemic issues rather than individual blame.