plan

Generate a structured Plan.md from approved shaping documents with milestones and rollout sections.

Updated Feb 27, 2026

Search Tags:#planning #documentation #milestones #plan #scope #project-management #shaping-doc

Ready to run

npx skills add https://github.com/dailydm/skills --skill plan-dailydm

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams convert approved Shaping documents into concrete planning artifacts, creating a clear roadmap for project work.

Core Features & Use Cases

Generate a structured Plan markdown document from an approved Shaping doc.
Ensure alignment between the Shaping doc and the project plan, including scope, milestones, and ownership.
Provide step-by-step guidance for planning activities, documentation standards, and artifact linking.

Quick Start

Create the plan.md file following the template and reference the approved Shaping doc.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I convert a shaping doc into a project plan?▼

To convert a shaping doc into a project plan, you generate a structured plan.md file that includes context, scope, milestones, technical approach, and rollout sections. This ensures your approved shaping document is translated into an actionable execution plan.

What is the best way to structure milestones from a shaping document?▼

Structuring milestones from a shaping document requires creating a standardized plan.md that explicitly defines project scope, ownership, and technical approach. This aligns your roadmap directly with the approved shaping doc for clear execution.

Does this project planning approach work without dependencies?▼

Yes, this project planning approach works without external dependencies because it focuses on generating a standardized markdown documentation format. It requires only an approved shaping doc as input to produce the actionable plan.md file.

Can I use markdown for project management documentation and scope alignment?▼

Yes, you can use markdown for project management documentation by generating a plan.md file. It enforces scope alignment by directly linking back to the shaping doc and standardizing sections for context, milestones, and technical rollout.

What sections do I need for a standardized plan.md file?▼

A standardized plan.md file requires specific sections for context, scope, milestones, technical approach, and rollout. Proper linking to the approved shaping doc is also required to ensure full project alignment and traceability.