pm-planner

Create atomic backlog tasks with measurable acceptance criteria.

50|9|Updated Oct 15, 2025

Search Tags:#acceptance criteria #SDD #backlog #task creation #feature decomposition #atomic tasks

Ready to run

npx skills add https://github.com/jpoley/flowspec --skill pm-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-planner
Source: https://github.com/jpoley/flowspec/tree/main/.claude/skills/pm-planner
Command: npx skills add https://github.com/jpoley/flowspec --skill pm-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PM Planner helps product teams craft backlog tasks that are atomic, well-scoped, and easily testable, reducing ambiguity and downstream rework.

Core Features & Use Cases

Task Creation: Generate clear backlog items with concise titles and rationale.
Feature Decomposition: Break large features into independent tasks that fit a single PR.
Acceptance Criteria: Provide measurable, testable criteria for each task.
Review & Quality: Help ensure tasks meet atomicity and value guidelines.

Quick Start

Create backlog task "Add user settings page" with AC: - [ ] User can update profile, - [ ] Page loads within 2 seconds.

Frequently Asked Questions about pm-planner

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

FAQPage Schema

How do I break down a large feature into atomic backlog tasks?▼

Feature decomposition splits large features into independent, single-PR tasks. Each atomic task should be testable and deliverable on its own, with clear acceptance criteria defining what done means. This reduces rework and keeps tasks focused.

What makes a backlog task well-scoped and testable?▼

Atomic tasks are independent, measurable, and fit a single PR. Write acceptance criteria as testable conditions—e.g., 'user can update profile' or 'page loads within 2 seconds.' Measurable criteria eliminate ambiguity and make review straightforward.

How do I write acceptance criteria that actually work?▼

Acceptance criteria must be testable and measurable, not vague. Use specific outcomes: 'user sees confirmation message' instead of 'improve user experience.' Each criterion should map to a single behavior, making QA and development alignment clear.

When should I review backlog tasks for quality?▼

Review tasks before they enter the sprint to catch scope creep, missing acceptance criteria, and dependencies. Atomic task reviews catch problems early, reduce downstream rework, and ensure tasks are truly independent and testable.

Can I use this approach for complex product features?▼

Yes. Complex features decompose into multiple atomic tasks, each with its own acceptance criteria. Break them until each task fits a single PR and one engineer can complete it independently without blocking others.