Epic Breakdown

Community

Productfculty-aipm

epic-breakdown

Use this skill when the user asks to "break this initiative into epics", "structure this as epics", "how should I organize this work", "help me sequence this initiative", "epic planning", "what are the phases of this project", "initiative breakdown", or has a large initiative and wants to decompose it into manageable, ship-able phases with clear sequencing.

Overview

Publisher	Productfculty-aipm
Repository	`PM-Copilot-by-Product-Faculty`
Skill name	`epic-breakdown`
Stars	80
Forks	34
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Productfculty-aipm on GitHub. Read the source before you install it.

Installation

Install the Epic Breakdown AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/epic-breakdown
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/epic-breakdown

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty.git /tmp/PM-Copilot-by-Product-Faculty
mkdir -p .claude/skills
cp -r /tmp/PM-Copilot-by-Product-Faculty/skills/epic-breakdown .claude/skills/epic-breakdown

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Epic Breakdown in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Epic Breakdown on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Epic Breakdown is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Epic Breakdown

You are helping the user decompose a large initiative into a sequenced set of epics — each of which delivers user value independently and can be shipped and measured before the next one begins.

Framework: Shape Up (appetite-based scoping), Lenny's PRD guide (just enough direction), iterative delivery principles.

Step 1 — Load Context

Read memory/user-profile.md for team size, current roadmap state, and any existing epics or initiatives in the Now/Next list. Read context/product/roadmap.md for OKR context.

Step 2 — Understand the Initiative

Extract from the user's description:

What is the full initiative (if shipped completely, what does it look like)?
What user problem does it solve?
What's the constraint: time, team size, or scope?
What would a "minimal first ship" look like?

Step 3 — Identify Natural Seams

Find the natural breaking points in the initiative — places where a partial version delivers real user value. These become epic boundaries.

Ask: "If we shipped only this piece, would users get real value? Or would it be invisible to them?"

Good epic breaks:

Complete user flow (even if limited) that a user can accomplish end-to-end
A new user segment being served for the first time
A new connection to an external tool that stands alone
A new mode or capability that can be toggled independently

Bad epic breaks:

Half a user flow (user can start but not finish)
Backend work with no user-visible output
A step that's only valuable in combination with the next step

Step 4 — Sequence the Epics

Order epics using these principles:

De-risk first: Tackle the epic with the most technical or user uncertainty first. Learn before you invest.
Value early: If possible, ship something users can use and give feedback on before the full initiative is complete.
Dependencies first: If Epic 2 depends on Epic 1's infrastructure, sequence accordingly.
80/20 rule: The first epic should deliver 80% of the user value in 20% of the work.

Step 5 — Epic Template

For each epic, fill in:

Epic name: [3–5 words, what it does] User value: [One sentence — what can users do after this ships that they couldn't before?] Scope: [What's included; what's explicitly excluded] Success metric: [How will we know this epic delivered value?] Size estimate: [Number of sprints / person-weeks — be explicit about assumptions] Dependencies: [What must be done before this epic can start?] Risks: [What could cause this epic to take 2× longer?] MVP vs. Full: [Is this epic the MVP version or the full version?]

Step 6 — Output

Produce:

Epic breakdown table (name, user value, size, sequence, status)
Sequencing rationale (why in this order?)
Ship plan: which epics can go live incrementally vs. need to wait for others
Recommendation for Epic 1 starting point (the minimum shippable first piece)
A question to validate sequencing: "Would you rather ship [Epic 1 value] in [Epic 1 time] and then [Epic 2 value], or wait to ship everything together? Why?"

Frequently asked questions

What does the Epic Breakdown AI skill do?

Why use Epic Breakdown on TypingMind?

Because you install it once and use it with any model. Epic Breakdown is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Epic Breakdown in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/epic-breakdown. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Epic Breakdown?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Epic Breakdown?

As many as you like. As long as a model supports skills, you can use Epic Breakdown with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Epic Breakdown AI skill free?

It is published on GitHub by Productfculty-aipm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Docker Patterns

affaan-m

CommunityPopular

Patrones de Docker y Docker Compose para desarrollo local, seguridad de contenedores, networking, estrategias de volúmenes y orquestación de múltiples servicios.

Architecture Decision Records

affaan-m

CommunityPopular

コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。

Automation Audit Ops

ECC用の証拠ベースの自動化インベントリとオーバーラップ監査ワークフロー。ユーザーがどのジョブ、フック、コネクタ、MCPサーバー、またはラッパーがライブか、壊れているか、冗長であるか、修正前に不足しているかを知りたい場合に使用します。

Grok

Delegate coding to xAI Grok Build CLI (features, PRs).

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Epic Breakdown

Step 1 — Load Context

Step 2 — Understand the Initiative

Step 3 — Identify Natural Seams

Step 4 — Sequence the Epics

Step 5 — Epic Template

Step 6 — Output

Frequently asked questions

Related AI Skills

Set up your own AI workspace now