functional-planner

Converts PRDs into validated work-item hierarchies for Azure DevOps, GitHub, or Jira.

1.4k|284|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/microsoft/hve-core --skill functional-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: functional-planner
Source: https://github.com/microsoft/hve-core/tree/main/.github/skills/project-planning/functional-planner
Command: npx skills add https://github.com/microsoft/hve-core --skill functional-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about functional-planner

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

FAQPage Schema
How do I turn a PRD into a work-item hierarchy?

Invoke the functional-planner skill with the PRD path or content and a target platform (ado, github, or jira). It runs a five-phase analysis and produces a plan file plus a reviewable handoff.md under the platform's prds tracking path.

Does this skill create issues in Azure DevOps, GitHub, or Jira?

No. The skill is strictly read-only and never creates, updates, transitions, comments on, or links work items. It produces planning artifacts that a separate Backlog Manager execution pass applies after user review.

Can I plan a backlog for Jira with this skill?

Yes. Jira planning requires JIRA_BASE_URL plus JIRA_API_TOKEN or JIRA_PAT, and the jira skill for command surfaces. Issue types and required fields are validated with read-only fields discovery before any create is proposed.

What happens when an issue type or field cannot be validated?

The item is marked needs_review and the affected hierarchy relationship is flattened rather than guessed. The plan never proposes a create against a type or field that read-only discovery could not confirm.

Which planning frameworks does the decomposition support?

Three lenses are included: a generic platform-native lens (default), a Scrum lens paraphrased from the Scrum Guide, and a Kanban lens paraphrased from the Kanban Guide. The platform reference always governs concrete type names and hierarchy rules.