dev-plan

Convert PRDs into structured execution plans with milestones and progress logs.

Updated Aug 27, 2026

Search Tags:#planning #templates #execution #milestones #plan #prds

Ready to run

npx skills add https://github.com/mattjefferson/agents --skill dev-plan-mattjefferson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-plan
Source: https://github.com/mattjefferson/agents/tree/main/skills/dev-plan
Command: npx skills add https://github.com/mattjefferson/agents --skill dev-plan-mattjefferson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Transform PRDs or feature descriptions into a self-contained, executable plan that guides teams from concept to implementation without needing external context.

Core Features & Use Cases

Converts a PRD into a structured, step-by-step execution plan using the standard plan template.
Accepts both file-based PRDs (e.g., docs/prds/xxx-prd.md) and inline descriptions to generate a living plan.
Produces milestones, a narrative progress log, and concrete guidance that can be handed off to engineering teams.

Quick Start

Provide a PRD file path or a brief inline description after the command to generate a living execution plan.

Frequently Asked Questions about dev-plan

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

FAQPage Schema

How do I turn a PRD into an actionable execution plan?▼

To turn a PRD into an execution plan, you provide a PRD file path or inline feature description to generate a structured, step-by-step living document with milestones for engineering handoff.

What is the best way to generate sprint milestones from product requirements?▼

Generating sprint milestones from product requirements involves loading a PRD and applying a plan template to produce concrete guidance and a narrative progress log for ongoing team reference.

Can I use inline feature descriptions to create a structured engineering plan?▼

Yes, you can use inline feature descriptions to create a structured engineering plan by applying a standard template that outputs a self-contained, actionable document ready for implementation.

Does this planning approach support both file-based PRDs and brief text inputs?▼

Yes, this planning approach supports both file-based PRDs, such as docs/prds/xxx-prd.md, and brief inline text descriptions to generate a living execution plan without needing external context.

Why use a living document for sprint planning instead of a static checklist?▼

A living document for sprint planning provides a narrative progress log and ongoing reference that adapts during implementation, unlike a static checklist, ensuring engineering teams maintain continuous context.