create-plan

Convert specification documents into structured implementation plans with phases, milestones, dependencies, and risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert a specification or requirements document into a concrete, phased implementation plan with milestones, dependencies, and risks.

Core Features & Use Cases

  • Phase generation: derive logical work phases from requirements and user stories.
  • Milestones & dependencies: assign milestones and map cross-phase dependencies.
  • Risk & deliverables: produce a risk register and a clear list of deliverables for each phase.

Quick Start

Provide a specification or requirements document, and the skill will generate a phased implementation plan with milestones, dependencies, and risks.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I turn software requirements into a phased implementation plan?

To turn requirements into a phased implementation plan, provide a specification document to generate logical work phases, milestones, cross-phase dependencies, and a risk register formatted as a structured plan output.

What is SDLC project scoping for feature rollouts?

SDLC project scoping for feature rollouts is the process of converting specifications into structured phases with clear milestones, dependencies, risk mitigations, and deliverables to guide software teams through implementation.

How do I generate a risk register and milestones from a specification document?

Generating a risk register and milestones from a specification document involves deriving logical work phases from user stories, mapping cross-phase dependencies, and producing a formatted plan output with identified risks and deliverables.

Can I use this for workflow orchestration and project scoping without external dependencies?

Yes, you can use this for workflow orchestration and project scoping without external dependencies, as it operates independently to convert requirements documents into phased plans with milestones, risks, and optional observability considerations.

Does the generated plan output include telemetry and observability considerations?

The plan output includes optional telemetry and observability considerations alongside the required phases, milestones, cross-phase dependencies, risk mitigations, and deliverables for each implementation stage.

What is the best way to map cross-phase dependencies for a software project?

The best way to map cross-phase dependencies for a software project is to derive logical work phases from requirements and user stories, then assign milestones to produce a structured plan output detailing these dependencies.