write-epic

Generate structured epic specifications with scope boundaries and dependencies.

4|Updated Mar 11, 2026

Search Tags:#specification #requirements #product management #scope #epic #project definition

Ready to run

npx skills add https://github.com/cpliakas/claude-code-engineering-leaders --skill write-epic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-epic
Source: https://github.com/cpliakas/claude-code-engineering-leaders/tree/main/skills/write-epic
Command: npx skills add https://github.com/cpliakas/claude-code-engineering-leaders --skill write-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you clearly define project epics by establishing a problem statement, success criteria, and explicit scope boundaries, preventing scope creep and ensuring strategic alignment.

Core Features & Use Cases

Epic Definition: Generates a structured epic specification.
Scope Management: Clearly defines what is in and out of scope, and identifies non-goals.
Risk Assessment: Outlines dependencies and potential risks.
Use Case: Before starting a large feature development, use this Skill to create a comprehensive epic document that aligns stakeholders and guides the development team.

Quick Start

Use the write-epic skill to define a new epic for user authentication with email and OAuth login.

Frequently Asked Questions about write-epic

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

FAQPage Schema

How do I define an epic specification to prevent scope creep in product management?▼

Defining an epic specification requires structuring a problem statement, success metrics, and explicit scope boundaries to prevent scope creep. This ensures strategic alignment by right-sizing multi-sprint initiatives and outlining dependencies and risks.

What should be included in project epics for large feature development?▼

Project epics for large feature development should include a problem statement, desired outcome, success metrics, scope boundaries, and dependencies. Identifying non-goals and potential risks aligns stakeholders and guides the development team.

How do I align a multi-sprint initiative with existing project documentation?▼

Aligning multi-sprint initiatives involves gathering context from project documentation like CLAUDE.md and roadmap files. This ensures the epic specification matches strategic goals and right-sizes the project scope accurately.

Can I manage scope boundaries and non-goals when defining project requirements?▼

Managing scope boundaries and non-goals is possible when defining project requirements by generating a structured epic specification. It clearly defines what is in and out of scope, ensuring development teams avoid unrelated work.

What is the best way to assess risks and dependencies for a new project epic?▼

Assessing risks and dependencies for a new project epic is best done by creating a comprehensive epic document. This document outlines potential risks and dependencies, aligning stakeholders before development begins.