create-plan

Create detailed implementation plans within milestone tracking workflows.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/itsjavi/skills --skill create-plan-itsjavi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/itsjavi/skills/tree/main/skills/create-plan
Command: npx skills add https://github.com/itsjavi/skills --skill create-plan-itsjavi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the creation and management of implementation plans within a defined planning workflow, streamlining the process and ensuring comprehensive documentation.

Core Features & Use Cases

  • Plan Creation: Facilitates the creation of detailed plans within an existing planning workflow.
  • Context Resolution: Helps identify the correct planning root and relevant context documents.
  • Content Formatting: Ensures plans include all necessary components such as status, goals, acceptance criteria, and risk notes.

Quick Start

Use the create-plan skill to create an implementation plan for a new feature in your project.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I automate implementation plan creation for programming workflows?

Automating implementation plan creation requires structured workflow documents like GUIDE.md and MILESTONES.md to identify planning roots, update milestone records, and generate comprehensive plan documents with goals and acceptance criteria.

What do I need to set up before creating detailed project plans in my workflow?

To create detailed project plans, you need established planning workflow documents, specifically GUIDE.md and MILESTONES.md files, which provide the necessary context for identifying planning roots and tracking milestones.

How does milestone tracking work during plan creation?

Milestone tracking during plan creation works by reading existing MILESTONES.md documents to resolve project context, then updating those milestone records to reflect the newly generated comprehensive implementation plan.

What components should be included in a detailed implementation plan?

A detailed implementation plan should include specific components such as status, goals, acceptance criteria, and risk notes to ensure comprehensive documentation within your established planning workflow.

Can I generate implementation plans without an existing project management workflow?

Generating implementation plans requires an existing project management workflow because the process depends on identifying a planning root and reading structured workflow documents like GUIDE.md and MILESTONES.md.

Why does plan creation fail to find the correct planning root context?

Plan creation fails to find the correct planning root context when required structured workflow documents, such as GUIDE.md and MILESTONES.md, are missing or improperly formatted within the project directory.