One-click install
npx skills add https://github.com/corticalstack/claude-code-flow --skill create-plan-corticalstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/corticalstack/claude-code-flow/tree/main/.claude/skills/create-plan
Command: npx skills add https://github.com/corticalstack/claude-code-flow --skill create-plan-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a GitHub issue or task into a phased, test-driven implementation plan by first researching the codebase and then specifying exactly what to build later—without writing any implementation code in the plan itself.

Core Features & Use Cases

  • Issue-to-plan workflow: Accepts a GitHub issue URL/number (or task context) and produces a concrete multi-phase plan stored under flow/plans/.
  • TDD-first planning: Enforces that every phase includes a failing-tests-first cycle (write tests, confirm failure, describe implementation, confirm pass).
  • Rename and reference rigor: For rename operations, requires comprehensive discovery of reference patterns (paths, descriptive text, hyphenated/compound names, config/documentation examples, imports, comments) and explicit replacement patterns plus verification commands.
  • Safety and scope control: Prohibits implementation code in the plan and avoids autonomous execution; it runs only when invoked via /create-plan or explicitly requested.

Quick Start

Invoke the skill with a GitHub issue reference like /create-plan #123 to generate a phased implementation plan for that work item.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I generate a TDD implementation plan from a GitHub issue?

To generate a TDD implementation plan from a GitHub issue, you can invoke the skill with an issue reference like /create-plan #123. It researches your existing codebase and outputs a phased, test-driven development plan without writing any implementation code.

How do I handle rename operations safely in an implementation plan?

Handling rename operations safely requires comprehensive discovery of reference patterns like paths, descriptive text, hyphenated names, config examples, imports, and comments. The plan must specify explicit replacement patterns and deterministic verification commands.

Does the implementation plan include writing actual code?

No, the implementation plan strictly prohibits writing implementation code. It applies strict no-code constraints to avoid autonomous execution, focusing solely on defining test-first guidance and checkable specifications for later implementation.

Can I use this workflow orchestration skill without any dependencies?

Yes, you can use this workflow orchestration skill without dependencies. It runs only when explicitly requested or invoked via /create-plan, requiring just a GitHub issue URL or task context to produce a multi-phase plan stored under flow/plans/.