pmagent

Generate sprint_x.md files with task breakdowns and acceptance criteria from Feature Contracts.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/ludsonaiello/lead360 --skill pmagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmagent
Source: https://github.com/ludsonaiello/lead360/tree/main/.claude/skills/pmagent
Command: npx skills add https://github.com/ludsonaiello/lead360 --skill pmagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PM Sprint Planner Agent reduces ambiguity in sprint planning by translating feature contracts and live codebase insights into production-ready sprint files that developers can execute without extra references.

Core Features & Use Cases

  • Generates self-contained sprint files for any module based on the Feature Contract.
  • Reads contracts and the live Lead360 codebase to enforce scope, RBAC, and architectural conventions.
  • Produces clear task breakdowns (migrations, DTOs, services, controllers, tests, and docs) with explicit acceptance criteria and gate markers.
  • Use Case: Given a new module or feature, output sprint_1.md outlining tasks and API surface, ready for backend and frontend sprints to execute.

Quick Start

Initialize the Claude session and request Sprint 1 for the pmagent skill by analyzing the contract and the live codebase.

Frequently Asked Questions about pmagent

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

FAQPage Schema
How do I generate a sprint plan from a feature contract and codebase?

To generate a sprint plan, you analyze the feature contract alongside the live codebase to produce self-contained sprint files. These files specify exact file names, method signatures, and acceptance criteria for developers to execute without external references.

What is automated sprint planning for backend modules?

Automated sprint planning translates feature contracts and codebase insights into production-ready sprint files. It reduces ambiguity by outputting complete task breakdowns including migrations, DTOs, services, controllers, and tests with explicit acceptance criteria.

How do I ensure Prisma queries include tenant_id filtering in sprint tasks?

Ensuring Prisma queries include tenant_id filtering is handled by embedding platform patterns directly into the generated sprint files. The sprint documents inline all rules and architectural conventions so developers apply tenant_id filtering automatically.

Can I use feature contracts to plan dependency-driven backend sprints?

Yes, feature contracts can plan dependency-driven backend sprints by providing explicit gate markers within the generated sprint files. These gate markers ensure tasks are ordered correctly and dependencies are resolved before subsequent sprint phases begin.

Does sprint planning work with Lead360 module architecture and RBAC?

Sprint planning works with Lead360 modules by reading contracts and the live codebase to enforce scope, RBAC, and architectural conventions. It generates sprint files that align with the platform's specific module structure and platform patterns.

What are the limitations of generating self-contained sprint files for codebases?

A limitation of generating self-contained sprint files is the dependency on having an accurate feature contract and accessible live codebase. Without these inputs, the sprint documents cannot correctly specify exact method signatures or enforce architectural conventions.