plan-create

Create planning phase directories, plan.md, and subplan task files from conversation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Materialize an active conversation into a structured planning phase on disk, generating a root plan and subplans.

Core Features & Use Cases

  • Create planning phase directories and plan.md from conversation
  • Scaffold subplans and task files according to discussion
  • Deterministic, script-driven planning with preconditions and templates

Quick Start

Run the plan-create skill on the current conversation to scaffold a new planning phase.

Frequently Asked Questions about plan-create

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

FAQPage Schema
How do I turn an active conversation into structured planning phases on disk?

To turn an active conversation into planning phases, the skill materializes discussion content into a deterministic filesystem structure, generating a root plan.md and subplan directories with task files.

How do I generate subplans and task files from architecture discussions?

Generating subplans and task files from architecture discussions requires running the skill on the current conversation to scaffold a new planning phase directory populated with standardized plan content templates.

How does deterministic planning compute the next phase number for task documentation?

Deterministic planning computes the next phase number by enforcing filesystem-based preconditions and using internal scripts to evaluate existing planning phase directories before creating the new phase-N folder.

Do I need any external dependencies to automate workflow planning from conversations?

No external dependencies are required to automate workflow planning from conversations. The skill operates independently using bundled scripts and references to scaffold the planning phase structure.

What is the best way to organize evolving architecture decisions into per-subplan directories?

The best way to organize evolving architecture decisions into per-subplan directories is using this script-driven approach, which standardizes plan content and enforces filesystem preconditions for deterministic task file generation.

Why does creating a planning phase require enforcing filesystem-based preconditions?

Creating a planning phase requires enforcing filesystem-based preconditions to ensure deterministic sequence numbering and prevent overwriting existing phase-N directories during the subplan scaffolding process.