From beta-planning
Plans an epic.html: user-facing direction, guard rails, and a breakdown into deployable, sequenced tasks. Use when 'beta new epic', 'beta epic', 'create epic', 'plan an epic'. Not for a single task (use beta-new-task).
How this skill is triggered — by the user, by Claude, or both
Slash command
/beta-planning:beta-new-epicThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create `docs/epics/$ID-$NAME/epic.html` — a high-level plan that sets the direction and guard rails for an initiative spanning multiple tasks, then breaks it into deployable, sequenced tasks.
Create docs/epics/$ID-$NAME/epic.html — a high-level plan that sets the direction and guard rails for an initiative spanning multiple tasks, then breaks it into deployable, sequenced tasks.
Part of the beta planning workflow. An epic sits above tasks: it frames the user-facing outcome and the constraints every task inherits, then decomposes the work. Each breakdown item is later planned with
/beta-new-task. See references/beta-workflow-overview.md for the downstream pipeline and references/epic-overview.md for what an epic is and how it differs from a task.
An epic works at a different altitude than a task. Hold the line on it:
/beta-new-task), or if it's so large it should be several epics.Scan skills -- check available skills for topic matches relevant to the initiative. Load any matched skills before proceeding.
Read project docs -- find and read project documentation relevant to the domain (READMEs, how-to guides, concept docs, CLAUDE.md) so the direction is grounded in how the system actually works.
Determine epic ID -- scan docs/epics/ for existing folders. Assign the next 3-digit sequential ID. If docs/epics/ doesn't exist, start at 001.
Derive epic name -- create a short kebab-case name from the initiative (e.g. partner-api-program).
Create epic folder -- mkdir -p docs/epics/$ID-$NAME
Create epic.html -- load the /planning-doc skill and follow its process to create epic.html in the epic folder. It will fetch llms.txt for the current component reference and version pin. Set the document title to $ID: $NAME, status to draft, and include pd-meta with id, name, kind: "epic", status planning, and created date.
Populate the tabs -- author the epic's tabs. Lead with the user-facing final shape; keep every tab at epic altitude.
See references/epic-tabs.md for what each tab focuses on and which component to reach for per element.
Resolve Open Questions -- an epic sets direction, so unstated direction is the main risk. Proactively surface assumptions about scope, sequencing, and guard rails, and resolve them by asking the user interactively (use AskUserQuestion if available). Update the doc as answers come in. Repeat until resolved or deferred.
Hard-stop -- present the completed epic.html to the user. Do NOT start planning tasks. Tell them: "Review epic.html. When ready, plan the first task with /beta-new-task and reference this epic."
npx claudepluginhub mistakenot/skills --plugin beta-planningProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.