In this article
Functional Planner
| Field | Value |
|---|---|
| Kind | agent |
| Source | .github/agents/project-planning/functional-planner.agent.md |
| Invocation | Selected from the chat agent picker as Functional Planner |
| Interactive | Yes |
What it does
Read-only Product Manager agent that analyzes PRDs and plans Azure DevOps, GitHub, or Jira work-item hierarchies without mutating a tracker
When to use it
Use Functional Planner to turn a PRD into a platform-appropriate work-item hierarchy without creating or modifying tracker items. It combines requirements, codebase context, and read-only discovery of related work. Use Backlog Manager to execute the resulting handoff after review.
How to use it
- Select
Functional Planner, supply the PRD, and confirm the Azure DevOps project, GitHub repository, or Jira project key. - Confirm the planning framework when the context does not determine it.
- Review the proposed hierarchy, requirement coverage, and validated types and fields. Unsupported fields remain
needs_review; contradictory requirements stop dependent planning. - Review the plan and handoff before passing them to Backlog Manager. No tracker mutation occurs in this planning session.
Example usage
Ask: "Plan a work-item hierarchy from requirements/import-prd.md for our confirmed GitHub repository. Discover related issues, map every requirement, and leave unsupported hierarchy choices for review. Do not create issues."
Expect a traceable hierarchy and execution handoff with explicit gaps. Success means every requirement maps to proposed work or a named unresolved item, and no planning identifier is mistaken for an existing tracker ID.