create-epic

Automate epic creation for Claude projects using gp epic:create.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ian97531/goodplan --skill create-epic-ian97531
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epic
Source: https://github.com/ian97531/goodplan/tree/main/skills/create-epic
Command: npx skills add https://github.com/ian97531/goodplan --skill create-epic-ian97531

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual epic creation is error-prone and slow when starting new projects or expanding existing ones. This skill standardizes how epics are created, initialized, and linked to project goals.

Core Features & Use Cases

  • Mode A creates a new project and the first epic; Mode B adds a new epic to an existing project.
  • Validates gp >= 1.0.0 and writes goal.md at .goodplan/epics/<name>/goal.md.
  • Writes updated project context so Claude can reason with current scope.

Quick Start

Determine Mode A or Mode B, capture the epic goal, and run the gp epic:create command to generate the epic and its goal file.

Frequently Asked Questions about create-epic

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

FAQPage Schema
How do I automate epic creation for a new Claude project?

To automate epic creation for a new project, use Mode A to capture your idea, initialize the project state, and run the gp epic:create command. This generates the epic and writes the goal file to the .goodplan directory.

Can I add a new epic to an existing project workflow?

Yes, you can add a new epic to an existing project using Mode B. This mode captures your new epic idea and runs gp epic:create to initialize the epic state and write its goal file without disrupting existing project context.

Do I need a specific version of gp to initialize project epics?

Yes, you need gp version 1.0.0 or higher to initialize project epics. The workflow validates your gp version before applying Mode A or Mode B to ensure proper creation of epic state and context files.

Where are epic goals and project context files stored during setup?

Epic goals and project context files are stored in conventional .goodplan paths. Specifically, the epic goal is written to .goodplan/epics/<name>/goal.md to ensure Claude can reason with the current scope.

What is the best way to standardize project epic setup and avoid errors?

The best way to standardize project epic setup is to use a guided CLI workflow that validates your environment and automates file generation. This prevents manual errors by consistently writing epic goals and updating project context.

Why does manual epic creation slow down project planning?

Manual epic creation slows down project planning because it is error-prone and requires repetitive setup for state initialization and linking goals. Automating this process with a CLI ensures standardization and faster project kickoff.