skills.rest
first-fluke
first-flukeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pm-agent

Decompose ambiguous product requirements into prioritized tasks with acceptance criteria.

218|33|Updated Jan 7, 2026
Search Tags:#planning#requirements#tasks#decompose#task-board#prioritize
One-click install
npx skills add https://github.com/first-fluke/fullstack-starter --skill pm-agent-first-fluke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-agent
Source: https://github.com/first-fluke/fullstack-starter/tree/main/.agent/skills/pm-agent
Command: npx skills add https://github.com/first-fluke/fullstack-starter --skill pm-agent-first-fluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PM Agent helps teams break down vague requests into concrete, testable tasks with clear ownership, priority, and dependencies, reducing planning latency.

Core Features & Use Cases

  • Task decomposition into discrete steps with owner, priority, and dependencies.
  • API-first planning and clear acceptance criteria for each task.
  • Output ready-to-run plans for orchestration with other agents.

Quick Start

Provide a feature brief and allow PM Agent to generate a prioritized task board with tasks, owners, and dependencies.

Frequently Asked Questions about pm-agent

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

FAQPage Schema
How do I decompose ambiguous product requirements into actionable tasks?▼

To decompose product requirements, provide a feature brief to generate a prioritized task board containing discrete tasks with clear owners, acceptance criteria, and dependencies.

What is the best way to prioritize tasks for sprint planning across cross-functional teams?▼

Prioritize tasks for sprint planning by feeding architecture decisions or feature requests into an API-first planning tool that generates records with priority, agent ownership, and orchestrator-ready plans.

How does task decomposition handle dependencies for orchestrator-ready plans?▼

Task decomposition handles dependencies by mapping relationships between discrete steps and generating an orchestrator-ready plan that clarifies execution order for cross-functional agents.

Can I use this approach for both feature requests and architecture decisions?▼

Yes, this approach applies to both feature requests and architecture decisions, breaking down vague inputs into testable tasks with clear ownership and API-first acceptance criteria.

Do I need a structured format to generate a prioritized task board?▼

No strict format is required. You simply provide a feature brief, and the system outputs a prioritized task board with titles, agents, dependencies, and acceptance criteria.

Why does planning latency increase with vague product requirements?▼

Planning latency increases because vague requirements lack clear ownership and testability, which this solves by generating concrete, prioritized task records with dependencies and acceptance criteria.

Related Skills

Explore More Product & Management Skills→
BrunoAMSilvaBrunoAMSilva

brainstorming

Generate structured alternatives with trade-off matrices and phased implementation plans.

Community
Intermediate
walker-hzxwalker-hzx

requirement-validation

Validate goals, scope, dependencies, risks, and acceptance criteria in requirements.

Community
Intermediate
script-reposcript-repo

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning via AI swarm coordination.

Community
Advanced
steelan9199steelan9199
9

task-sop-architect-yashu

Convert unstructured user requests into formal Standard Operating Procedures with task decomposition and risk management.

Community
Intermediate