plan-create-component

Generate a nine-section component plan template for GitHub issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? This Skill streamlines the process of adding new components to the project plan by generating a structured plan.md file and guiding its integration into the existing planning hierarchy. It automates plan creation, saving time and ensuring consistency.

Core Features & Use Cases:

  • Plan Generation: Creates new component plans following the 9-section Template 1 format, ensuring comprehensive planning.
  • Hierarchy Integration: Guides on updating parent plans and regenerating GitHub issues to reflect new components, maintaining project structure.
  • Use Case: You need to add a new "Tensor Operations" component to your shared library. Use this skill to generate the component's plan, then follow the steps to integrate it into the parent plan and update associated GitHub issues, ensuring a cohesive project structure.

Quick Start: Use the plan-create-component skill to create a new component plan for "Tensor Operations" under "notes/plan/02-shared-library/01-core".

Frequently Asked Questions about plan-create-component

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

FAQPage Schema
How do I automate creating a structured component plan in GitHub?

This Skill automates component plan creation by generating a GitHub issue-based template following a nine-section format. It saves time and ensures consistency across your project's planning hierarchy by standardizing plan structure, relative links, and integration with parent workflows.

What's the process for adding a new component to an existing project plan hierarchy?

Generate the component plan using this Skill, then update the parent plan and regenerate associated GitHub issues to reflect the new component. This maintains your project structure and ensures the new component integrates cohesively with existing plans and child relationships.

Can I use this for managing parent-child component relationships in documentation?

Yes. The Skill handles updating parent and child relationships, inputs, outputs, steps, and success criteria within the plan hierarchy. It enforces structured formatting and relative links to keep component relationships consistent across your documentation.

Does this Skill work with GitHub workflows and issue-based planning?

Yes. It integrates with GitHub workflows, scripts, and issue templates as part of your component-planning workflow. The generated plans use GitHub issue formats and work with replacement workflows for plan generation, regeneration, and validation.

What format does the generated component plan follow?

Plans follow a structured nine-section template format enforced by this Skill. The output is a `plan.md` file with standardized sections, relative links, and integration points designed to work within the planning hierarchy and GitHub issue workflow.

When should I use component planning instead of unstructured documentation?

Use component planning when you need to manage multiple interconnected components with defined inputs, outputs, success criteria, and hierarchical relationships. It ensures consistency, traceability, and integration across a shared library or project structure.