What problem does it solve?
Turning a Product Requirements Document into a tracker-ready backlog is error-prone: teams guess at issue types, hierarchy rules, and required fields, then discover mismatches only after creating items. This Skill performs read-only PRD-to-work-item planning, validating every type, field, and parent linkage against the target platform before anything is created.
Core Features & Use Cases
- Five-phase PRD decomposition: Analyzes the PRD, discovers codebase context and related work items, refines the hierarchy, and produces a reviewable handoff plan.
- Multi-platform validation: Applies per-platform hierarchy rules for Azure DevOps (Epic/Feature/User Story), GitHub (sub-issues and issue types), and Jira (Epic/Story/Task/Sub-task), using only read-only discovery calls.
- Framework lenses: Shapes decomposition with a generic platform-native lens, a Scrum lens, or a Kanban lens depending on how the team plans.
- Use Case: Given a PRD for a new feature, generate a validated Epic/Story breakdown for Jira with a handoff.md that a separate execution pass creates after user review.
Quick Start
Ask the agent to plan a work-item hierarchy from your PRD file for your target platform, for example by invoking the functional-planner skill with the PRD path and platform such as ado, github, or jira.