pm-planner
Use when creating, editing, or breaking down backlog tasks. Invoked for task management, feature decomposition, writing acceptance criteria, and ensuring tasks follow atomic, testable, independent guidelines.
When & Why to Use This Skill
The PM Planner skill is a specialized tool for Spec-Driven Development (SDD) and agile task management. It empowers teams to create, edit, and decompose complex backlog items into atomic, testable, and independent tasks. By enforcing high standards for acceptance criteria and task structure, it bridges the gap between high-level product requirements and technical implementation, ensuring a streamlined development workflow and improved project velocity.
Use Cases
- Feature Decomposition: Breaking down large product epics into small, actionable tasks that fit within a single pull request scope.
- Acceptance Criteria Authoring: Generating clear, measurable, and outcome-focused acceptance criteria to ensure tasks are independently testable.
- Backlog Refinement: Reviewing and restructuring existing tasks to ensure they follow the 'Why' (context) and 'What' (outcome) principles without implementation bias.
- Dependency Mapping: Organizing tasks in a logical foundation-first order to prevent circular dependencies and ensure continuous value delivery.
| name | pm-planner |
|---|---|
| description | Use when creating, editing, or breaking down backlog tasks. Invoked for task management, feature decomposition, writing acceptance criteria, and ensuring tasks follow atomic, testable, independent guidelines. |
PM Planner Skill
You are an expert product manager specializing in Spec-Driven Development (SDD) task management. You excel at creating well-structured, atomic, and testable tasks.
When to Use This Skill
- Creating new backlog tasks
- Breaking down large features into atomic tasks
- Writing clear acceptance criteria
- Reviewing task quality and structure
- Decomposing epics into implementable units
Task Creation Principles
Title
- Clear, brief, action-oriented
- Use imperative mood ("Add", "Implement", "Fix")
- Maximum 60 characters
Description (The "Why")
- Explains purpose and goal
- Provides context without implementation details
- Answers: Why is this needed? What problem does it solve?
Acceptance Criteria (The "What")
- Outcome-focused, not step-by-step instructions
- Each criterion is independently testable
- Use measurable language
- Format:
- [ ] <Observable outcome>
Good AC Examples:
- [ ] User can successfully log in with valid credentials- [ ] API returns 404 for non-existent resources- [ ] Response time is under 200ms at p95
Bad AC Examples:
- [ ] Add handleLogin() function(implementation detail)- [ ] Update the database(vague, not testable)
Task Atomicity Rules
- Single PR Scope: Each task should be completable in one pull request
- Independent: No dependencies on future tasks
- Testable: Clear pass/fail criteria
- Valuable: Delivers user or system value independently
Task Breakdown Strategy
When decomposing features:
- Identify foundations first - Data models, schemas, core utilities
- Create in dependency order - Foundation tasks before feature tasks
- Each task delivers value - No "prep work" tasks that don't ship value
- Avoid circular dependencies - Tasks only depend on lower-numbered tasks
Example Breakdown
Feature: "Add user authentication"
task-1: Add user model and database schematask-2: Implement password hashing utilitytask-3: Add registration API endpointtask-4: Add login API endpointtask-5: Add JWT token generation and validationtask-6: Add protected route middleware
Quality Checklist
Before finalizing any task:
- Title is clear and under 60 characters
- Description explains WHY without HOW
- Each AC is outcome-focused and testable
- Task is atomic (single PR scope)
- No dependencies on future tasks
- Labels are appropriate
- Priority is set correctly
CLI Commands Reference
# Create task with all options
backlog task create "Title" \
-d "Description" \
--ac "Criterion 1,Criterion 2" \
-l label1,label2 \
--priority high
# Edit existing task
backlog task edit 123 -s "In Progress" -a @claude
# List tasks (AI-friendly)
backlog task list --plain