planner

Convert product requirements into testable sprint contracts with acceptance criteria.

1|1|Updated Mar 25, 2026

Search Tags:#planning #project management #requirements #agile #sprint breakdown

Ready to run

npx skills add https://github.com/scottconverse/productteam --skill planner-scottconverse

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/scottconverse/productteam/tree/main/skills/planner
Command: npx skills add https://github.com/scottconverse/productteam --skill planner-scottconverse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams break down complex feature requests and PRDs into clear, testable sprint deliverables, facilitating efficient planning and execution.

Core Features & Use Cases

Requirement Decomposition: Converts high-level descriptions into precise files, descriptions, and acceptance criteria.
Dependency Identification: Determines prerequisite resources and files needed before starting.
Sprint Sizing: Guides sizing of scope based on lines of code and deliverables complexity.
Use Case: When tasked with building a new API endpoint, this Skill enables the team to define each file's purpose, acceptance criteria, dependencies, and scope, ensuring manageable and well-organized sprints.

Quick Start

Use the planner skill to generate a sprint plan for implementing a user login feature based on an existing PRD document.

Frequently Asked Questions about planner

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

FAQPage Schema

How do I break down product requirements into testable sprint contracts?▼

To break down product requirements into testable sprint contracts, you convert high-level feature specifications into precise file descriptions, acceptance criteria, and dependency lists. This decomposition ensures engineering teams organize incremental development work efficiently.

What is the best way to size sprints based on lines of code and deliverable complexity?▼

Sizing sprints based on lines of code and deliverable complexity involves evaluating the detailed scope of decomposed requirements. You guide sprint sizing by mapping prerequisite resources and files against the overall complexity of the feature specifications.

How do I identify prerequisite dependencies before starting a sprint?▼

Identifying prerequisite dependencies before starting a sprint requires analyzing existing code patterns and feature specifications. You determine necessary resources and files needed before starting to ensure the scope remains feasible and manageable.

Can I use this approach to plan a new API endpoint from an existing PRD?▼

Yes, you can use this approach to plan a new API endpoint from an existing PRD document. The process defines each file's purpose, acceptance criteria, dependencies, and scope, ensuring well-organized and incremental development sprints.

What do I need to generate a sprint plan for complex feature requests?▼

To generate a sprint plan for complex feature requests, you need predefined existing code patterns, clear acceptance criteria, and high-level product requirements. These inputs ensure feasible scope and facilitate efficient planning and execution.

When should I avoid breaking down a PRD into sprint deliverables?▼

You should avoid breaking down a PRD into sprint deliverables if predefined existing code patterns, dependencies, and clear acceptance criteria are not available. Without these inputs, ensuring a feasible scope for the incremental development work is difficult.