plan-md

Generate a detailed Markdown implementation plan with goals, dependencies, and phased rollout.

1|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/masta-g3/rules --skill plan-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-md
Source: https://github.com/masta-g3/rules/tree/main/skills/plan-md
Command: npx skills add https://github.com/masta-g3/rules --skill plan-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and documenting complex work is error-prone without a structured Markdown plan; this skill helps create a clear, maintainable implementation plan for a feature or task.

Core Features & Use Cases

  • Generates a comprehensive Markdown plan with sections for goals, approaches, dependencies, risk, and phased rollout.
  • Provides guidance on plan file naming, context files, and pending status preservation, plus review hooks for non-trivial plans.
  • Useful for teams coordinating feature work, epics, and tickets, ensuring alignment across stakeholders and engineers.

Quick Start

Follow the plan template to craft a detailed Markdown plan for the requested feature, ensuring scope is constrained and all critical steps are documented.

Frequently Asked Questions about plan-md

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

FAQPage Schema
How do I create a structured markdown implementation plan for a complex feature?

To create a structured markdown implementation plan, this skill generates a comprehensive document with sections for goals, approaches, dependencies, risk, and phased rollout. It requires a plan file location, context files, and execution guidelines to anchor planning scenarios.

What is the best way to document project management workflows in markdown?

Documenting project management workflows in markdown requires structuring phased execution guidelines and review steps. This skill maintains a pending status until execution and provides guidance on plan file naming and context files to ensure alignment across stakeholders.

Can I use existing feature tickets to anchor planning scenarios for new tasks?

Yes, you can use existing feature tickets or a features.yaml file to anchor planning scenarios for new tasks. This skill references these context files to ensure clear scope and actionable steps for features of varying complexity.

How do I maintain pending status and review hooks for non-trivial markdown plans?

To maintain pending status and review hooks for non-trivial markdown plans, the skill preserves the pending state until execution begins. It provides specific review steps for non-trivial plans to maintain clear scope and document critical steps.

What should a phased rollout plan in markdown include for coordinating team epics?

A phased rollout plan in markdown for coordinating team epics should include goals, approaches, dependencies, and risk sections. This skill generates the plan with phased execution guidelines and review hooks to ensure alignment across engineers.