pm-agent

Decompose complex requirements into prioritized JSON plans and task-board.md files with API contracts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/magisph/rv-adv --skill pm-agent-magisph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-agent
Source: https://github.com/magisph/rv-adv/tree/main/.agent/skills/pm-agent
Command: npx skills add https://github.com/magisph/rv-adv --skill pm-agent-magisph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill breaks down complex feature requests and product requirements into manageable, actionable tasks, complete with priorities and dependencies, ensuring efficient project planning and execution.

Core Features & Use Cases

  • Requirement Decomposition: Transforms high-level ideas into granular tasks.
  • Task Prioritization & Dependency Mapping: Organizes work for optimal workflow.
  • API Contract Definition: Ensures clear interfaces before implementation.
  • Use Case: A product manager can input a new feature request like "Implement user profile editing" and the agent will output a detailed plan including tasks for backend API development, frontend UI implementation, and necessary security considerations.

Quick Start

Use the pm-agent to break down the requirement "Create a user authentication system with email and password login".

Frequently Asked Questions about pm-agent

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

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

To decompose complex product requirements into actionable tasks, you can input a high-level feature request to generate a granular task list. The output defines priorities and dependencies, ensuring each task is small enough for single-agent execution.

What is API-first design in project planning and sprint preparation?

API-first design in project planning involves defining clear interface contracts before any implementation begins. This approach ensures structured sprint planning by establishing data boundaries and dependencies upfront, preventing integration bottlenecks later.

How do I map task dependencies when breaking down a feature request?

Mapping task dependencies during requirement decomposition organizes your workflow by linking sequential and parallel tasks. The generated plan automatically defines these relationships, optimizing the execution order for backend API development and frontend UI implementation.

Can I use this approach to plan both backend API development and frontend UI implementation?

Yes, you can use requirement decomposition to plan both backend API development and frontend UI implementation. By inputting a feature request, the output generates a comprehensive plan that separates backend contracts from frontend tasks while mapping their dependencies.

What is the best way to structure tasks for single-agent execution?

The best way to structure tasks for single-agent execution is to ensure each decomposed task is granular and self-contained. This method generates a JSON plan and a task-board file, keeping actions focused and compatible with orchestrator workflows.