pm-plan

Generate structured implementation plans with steps, dependencies, tests, and risk mitigations.

2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/pmatos/skills --skill pm-plan-pmatos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-plan
Source: https://github.com/pmatos/skills/tree/main/pm-plan
Command: npx skills add https://github.com/pmatos/skills --skill pm-plan-pmatos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan-first, structured thinking converts vague software requests into detailed, executable plans that guide multi-step work, risk assessment, and traceable execution.

Core Features & Use Cases

  • Generates end-to-end implementation plans from user prompts, including steps, dependencies, tests, and risk mitigations.
  • Supports planning scenarios such as feature design, refactors, migrations, migrations with cross-cutting concerns, and architecture exploration with a read-only planning discipline.
  • Produces a reproducible plan artifact stored as .ultraplan/<plan-name>.md, with explicit file references, validation, and hosting in the planning workspace.

Quick Start

Describe a thorough, multi-phase plan for the requested feature, including file references and a testing strategy, using the .ultraplan workflow.

Frequently Asked Questions about pm-plan

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

FAQPage Schema
How do I generate a structured implementation plan for a software feature?

To generate a structured implementation plan, describe your software request prompt to outline steps, dependencies, tests, and risk mitigations, producing a formal plan artifact with explicit file references and a validation checklist for execution.

What is read-only planning discipline in software architecture exploration?

Read-only planning discipline in architecture exploration involves generating end-to-end implementation plans and risk mitigations without modifying the codebase, producing a reproducible plan artifact stored as .ultraplan/<plan-name>.md to guide execution.

Can I use this approach for migrations with cross-cutting concerns?

Yes, this planning approach supports migrations with cross-cutting concerns, refactors, and feature design by converting vague software requests into detailed, executable plans with traceable execution and risk assessment.

What's the best way to document codebase exploration and risk management?

The best way to document codebase exploration and risk management is by generating a reproducible plan artifact stored as .ultraplan/<plan-name>.md, which includes explicit file references, dependencies, and a validation checklist for traceable execution.

Does this planning workflow require any specific dependencies?

No, this planning workflow requires no specific dependencies, allowing you to directly convert vague software requests into structured, multi-phase plans with risk assessment and validation checklists.