create-plan

Transform a feature specification into implementation-ready planning artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build complete implementation plans from a feature spec using the plan template, producing phase artifacts and a readiness report. Use this whenever the user asks for implementation planning, architecture planning, research-before-build, or preparation for task breakdown (even if they do not explicitly say "create-plan").

Core Features & Use Cases

  • Load context and read a feature spec
  • Generate plan.md from the plan template
  • Create research.md, data-model.md, quickstart.md, and contracts/ when external interfaces are in scope
  • Run pre-research and post-design gates to verify AGENTS.md constraints

Quick Start

Provide a spec_file path to the feature specification to generate a complete planning package in the feature workspace.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I turn a feature spec into an actionable implementation plan?

To turn a feature spec into an actionable implementation plan, provide a spec file path to generate a complete planning package, including plan.md, research.md, and data-model.md, in the feature workspace.

What's the best way to research external interfaces before building a feature?

Researching external interfaces before building involves consulting official documentation for technology decisions and recording cited sources in research.md, enforced by a pre-research gate to verify constraints.

How do I generate data models and contracts from a feature specification?

Generating data models and contracts from a feature specification produces data-model.md and a contracts/ directory automatically when external interfaces are in scope during the planning phase.

Do I need a spec file to create architecture documentation and phase artifacts?

Yes, creating architecture documentation and phase artifacts requires a spec file path to load context and apply post-design gates for readiness verification.

Can I use this for task breakdown preparation without explicit planning commands?

Yes, you can use this for task breakdown preparation when asked for architecture planning or research-before-build, even without explicitly issuing a create-plan command.

Why does implementation planning require checking AGENTS.md constraints?

Implementation planning requires checking AGENTS.md constraints through pre-research and post-design gates to verify project readiness and ensure generated artifacts align with architectural rules.