skills.rest
chenluhan
chenluhanCOMMUNITY
Explore all skills by this author →
GitHub

pm-delivery-breakdown

Break product handoffs into an Epic, Stories, acceptance criteria, dependencies, and handoff notes.

Updated Apr 15, 2026
Search Tags:#workflow#handoff#epic#product-management#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/chenluhan/skill --skill pm-delivery-breakdown
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-delivery-breakdown
Source: https://github.com/chenluhan/skill/tree/main/.agents/skills/pm-delivery-breakdown
Command: npx skills add https://github.com/chenluhan/skill --skill pm-delivery-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a PM handoff into an execution-ready structure: epics, stories, acceptance criteria, dependencies, and handoff notes.

Core Features & Use Cases

  • Epic, Stories, and tasks breakdown: Convert a product initiative into an engineering-ready plan with clear scope and ownership.
  • Handoff-ready artifacts: Generates dependencies, acceptance criteria, and integration notes for teams.
  • Use Case: Product manager asks to split a feature into implementable work units; the skill outputs an Epic, multiple Stories, and acceptance criteria with dependencies.

Quick Start

Prompt the system to break a feature into an Epic, Stories, acceptance criteria, dependencies, and handoff notes.

Frequently Asked Questions about pm-delivery-breakdown

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

FAQPage Schema
How do I break down a product feature into epics and user stories for engineering handoff?▼

To break down a product feature for engineering handoff, convert the product initiative into an execution-ready plan by splitting it into one Epic, multiple user Stories, clear acceptance criteria, and named dependencies.

What is the best way to write acceptance criteria and dependencies for a product roadmap release?▼

Writing acceptance criteria and dependencies for a roadmap release involves generating handoff-ready artifacts that define clear scope and ownership, ensuring engineering teams understand integration requirements before implementation begins.

How do I structure product handoffs to ensure engineering teams receive clear implementation scope?▼

Structuring product handoffs requires outputting a single Epic, a set of Stories with detailed acceptance criteria, explicitly named dependencies, and integration handoff notes to enable engineering teams to execute the plan.

Can I use this approach to split a large product initiative into implementable work units?▼

Yes, you can split a large product initiative into implementable work units by breaking the PM handoff into an execution-ready structure that includes Stories, acceptance criteria, and dependencies for clear ownership.

What should be included in a Build Pack-style engineering breakdown for software projects?▼

A Build Pack-style engineering breakdown should include an Epic, a set of Stories with acceptance criteria, clearly named dependencies, and handoff notes to enable engineering teams across software projects.

Why do I need to define dependencies and handoff notes when planning a feature release?▼

Defining dependencies and handoff notes during feature release planning is necessary to generate handoff-ready artifacts that prevent integration blockers and ensure engineering teams have clear scope and ownership.

Related Skills

Explore More Product & Management Skills→
kryptobaseddevkryptobaseddev
160

ct-epic-architect

Plan epics and decompose initiatives into atomic tasks with dependencies and waves.

Community
Advanced
ripabakripabak

breakdown-feature-prd

Generate structured PRD documents from Epic summaries for engineering teams.

Community
Advanced
tronghieutronghieu
36

bmad-sprint-status

Summarize sprint progress and detect delivery risks from sprint-status.yaml.

Community
Intermediate
DavidsonGomesDavidsonGomes

evo-create-epics-and-stories

Structure product requirements into epics and user stories with acceptance criteria.

Community
Advanced