epic

Create or update epic-style feature files with high-level project requirements.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tdp1999/claude-code-ctx --skill epic-tdp1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic
Source: https://github.com/tdp1999/claude-code-ctx/tree/main/plugins/ctx/skills/epic
Command: npx skills add https://github.com/tdp1999/claude-code-ctx --skill epic-tdp1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a raw feature idea into a structured epic with high-level requirements, enabling clearer planning and better alignment with project context.

Core Features & Use Cases

  • Create new epics from ideas and save them under .context/plans/epic-<name>.md
  • Update existing epics with expanded scope, added risks, and a changelog
  • Forecast technical considerations and flag potential domain-model implications to maintain alignment with architecture and vision

Quick Start

Provide a feature idea to /ctx:epic to generate a new epic document in .context/plans.

Frequently Asked Questions about epic

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

FAQPage Schema
How do I structure a raw product idea into high-level requirements for roadmapping?

To structure a raw product idea into high-level requirements, you can expand it into an epic file. This process refines the idea with clarifying questions and forecasts technical risks to align with your project context.

What is the best way to update an existing epic with expanded scope and new risks?

Updating an existing epic involves adding expanded scope, new risks, and a changelog to the feature file. This maintains alignment with the project's vision and architecture documents while tracking domain-model implications.

Can I generate epic files from feature ideas using existing vision and architecture docs?

Yes, you can generate epic files using existing vision and architecture docs. The system applies project context from these documents to ensure idea refinement and risk forecasting align with your broader product strategy.

How do I forecast technical considerations and domain-model implications for a new feature?

To forecast technical considerations and domain-model implications for a new feature, expand the idea into a structured epic. This process flags potential architecture misalignments and saves the output under .context/plans.

Where are generated epic documents saved when creating structured product requirements?

Generated epic documents are saved as markdown files under the .context/plans directory. Specifically, new epics are created using the .context/plans/epic-<name>.md file format for structured product requirements.

Does structuring epics require manual alignment with project architecture and vision docs?

No, structuring epics does not require manual alignment with project architecture and vision docs. The process automatically applies project context from these documents to guide idea refinement and maintain architectural alignment.