phase-plan-generate

Generate plan.md files with a 9-section Template 1 structure.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ml-odyssey --skill phase-plan-generate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase-plan-generate
Source: https://github.com/mvillmow/ml-odyssey/tree/main/.claude/skills/phase-plan-generate
Command: npx skills add https://github.com/mvillmow/ml-odyssey --skill phase-plan-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? This Skill automates the generation of comprehensive plan documentation following a strict 9-section format (Template 1), ensuring consistency, clarity, and easy conversion into actionable GitHub issues. It streamlines planning, saving time and reducing complexity.

Core Features & Use Cases:

  • Template-Based Generation: Creates new plan.md files from a standard template, ensuring all required sections are present.
  • Hierarchy Integration: Guides on maintaining parent/child relationships within the plan structure for organized project management.
  • Use Case: When starting a new project component, use this skill to generate a new plan.md file. It will provide the complete 9-section structure, prompting you to define objectives, inputs, outputs, and success criteria, ensuring a thorough plan.

Quick Start: Use the phase-plan-generate skill to generate a new plan for 'tensor-operations' under 'notes/plan/02-shared-library/01-core'.

Frequently Asked Questions about phase-plan-generate

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

FAQPage Schema
How do I generate a structured project plan documentation automatically?▼

Generate structured project plan documentation using the 9-section Template 1 format, which creates comprehensive plan.md files with enforced sections for objectives, inputs, outputs, and success criteria. This ensures consistency and converts plans into actionable GitHub issues.

What should be included in a plan.md file for project planning?▼

A plan.md file following Template 1 must include 9 mandatory sections covering objectives, scope, inputs, outputs, success criteria, and hierarchy relationships. The structure requires explicit relative links and verifiable success metrics before implementation begins.

When should I use planning documentation templates for new components?▼

Use planning documentation templates when starting a new project component or subsection to establish a thorough plan before implementation. Template-based generation ensures all required planning specifications and success criteria are defined upfront, reducing scope creep and rework.

Can I maintain parent-child relationships within my project plan structure?▼

Yes, plan.md generation supports hierarchy integration by guiding you to maintain explicit parent-child relationships within the plan structure. This organizes project components hierarchically and ensures alignment across nested planning documents.

What's the best way to streamline project planning and reduce documentation complexity?▼

Automate comprehensive plan documentation generation using standardized templates to enforce consistent structure across all project components. Template-based planning saves time, eliminates manual formatting, and reduces complexity by providing a repeatable framework.

Does plan generation require any prerequisites or specific input formats?▼

Plan generation requires you to define core inputs: project component name, parent directory hierarchy, and planning phase context. No external dependencies are needed; the Skill generates the complete 9-section template structure prompting you to populate each mandatory section.