create-epic

Name: create-epic
Author: aleksander-dytko

31stars4forks

How to install create-epic?

aleksander-dytko/ai-pm-workspace/create-epic

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill create-epic

Installs into the current project.

Summary

Turn an idea into a structured epic draft using templates/epic-template.md

Files · 1

View on GitHub

SKILL.md

1	# Create Epic
2
3	You help turn a raw product idea into a well-structured epic draft. The output follows `templates/epic-template.md` and lands in `epics/` with `stage: Explore`.
4
5	## Input
6
7	The user provides via `$ARGUMENTS`:
8	- A short prompt (e.g., "unified onboarding dashboard for CSMs"), OR
9	- A path to a raw idea note (e.g., `samples/sample-epic-idea.md`)
10
11	## Workflow
12
13	### 1. Gather context
14
15	Read the raw idea. If `$ARGUMENTS` is a path, read that file. Otherwise use the prompt directly.
16
17	Read supporting context in parallel:
18	- `templates/epic-template.md` - the target structure
19	- `docs/epic-lifecycle.md` - the stage framework
20	- `research/personas/` - personas that might match the target user
21	- `Dashboard/people-profiles.md` - any stakeholders mentioned
22	- `Loose Notes/Work/` and `Meetings/` - related prior discussions (search by keywords from the idea)
23	- `Initiatives/` - does this fit under an existing initiative?
24
25	### 2. Identify gaps in the idea
26
27	Before drafting, identify what's missing or unclear. Ask the user 3-5 focused questions in ONE `AskUserQuestion` round if any of these are unclear from the raw input:
28
29	- Target user: which persona does this serve? (Offer personas from `research/personas/` as options.)
30	- Primary metric: what measurable outcome should improve?
31	- Scope boundary: what is explicitly NOT in this epic?
32	- Initiative fit: does this belong under an existing initiative (show list from `Initiatives/`) or does it stand alone?
33	- Competitor check: has competitive research been done? (Offer `/competitive-research` if not.)
34
35	Skip questions where the raw idea already has a clear answer. Maximum one round.
36
37	### 3. Draft the epic
38
39	Use `templates/epic-template.md` as the structure. Fill what you can from the raw idea + answers:
40
41	Required sections (always fill):
42	- Value Proposition Statement - one crisp statement of the outcome.
43	- User Problem - 1-2 paragraphs from the customer's perspective. Frame from the "why", not the product's failure.
44	- User Stories - 3-6 stories at the "what" level (Explore phase). Add the "how" later.
45
46	Phase-specific (fill lightly in Explore, flag for Scope):
47	- Breakdown - list sub-activities under Explore (customer interviews, research, opportunity-solution tree).
48	- Risk Assessment - initial class only, full in Scope.
49
50	Skip for now:
51	- Release Notes (drafted in Scope or later).
52	- Implementation Notes (Scope phase).
53	- Design Planning, Documentation Planning (Scope phase).
54	- Validation Criteria (Validate phase).
55
56	Fill placeholders honestly. If you don't know something, write `[To determine during Scope]` or `[Needs user research]`. Don't fabricate.
57
58	### 4. File location and naming
59
60	- Folder: `epics/`. Create if it doesn't exist.
61	- Filename: `YYYY-MM-DD - [Epic Title slug].md`. Example: `2026-04-20 - Unified onboarding dashboard.md`.
62	- Frontmatter: set `stage: Explore`, `status: exploring`, `created: YYYY-MM-DD`.
63
64	### 5. Link the epic
65
66	- Daily journal: add a link in today's journal under `## Notes`. Format: `- [[YYYY-MM-DD - Epic Title]] - new epic in Explore stage`.
67	- Initiative: if the epic fits under an existing initiative (from step 2), add a link in the initiative file under `## Epics under this initiative`.
68	- Nothing external: do NOT push to any external tracker. The epic lives in the vault until you explicitly ship it elsewhere.
69
70	### 6. Propose follow-up tasks
71
72	Based on what's missing in the draft, propose 2-5 tasks that would move the epic out of Explore. Examples:
73
74	- Schedule 5 customer interviews with target persona
75	- Run `/competitive-research` on [topic]
76	- Run `/opportunity-solution-tree` for the primary metric
77	- Review the draft with [stakeholder]
78	- Draft a 3-bullet research brief for the user research team
79
80	Show the proposed task list and wait for user confirmation. After confirmation, append to `Dashboard/tasks.md` under "This week" with format:
81
82	```
83	- [ ] Task - source: [[YYYY-MM-DD - Epic Title]] - due: YYYY-MM-DD - priority: P3
84	```
85
86	### 7. Output summary
87
88	```
89	✅ Epic drafted: [[YYYY-MM-DD - Epic Title]]
90	✅ Linked in today's journal
91	[if initiative match] ✅ Linked under [[Initiative]]
92
93	Stage: Explore
94	Status: exploring
95
96	📋 Proposed follow-up tasks (to move to Scope):
97	1. [Task]
98	2. [Task]
99
100	Confirm: Add tasks to Dashboard/tasks.md? (Y/N)
101
102	💡 Next steps in the lifecycle: see docs/epic-lifecycle.md
103	```
104
105	## Notes
106
107	- Honesty over completeness. It's better to mark a section as `[Needs user research]` than to invent answers.
108	- Epics start thin and grow. The Explore-stage draft should be under 1 page. Sections get filled as the epic progresses.
109	- One initiative per epic. If the idea fits under multiple initiatives, flag this as a scope problem rather than dual-linking.
110	- **User stories f

People who liked this also viewed

6 picks

Type

create-epic

31stars4forks

View on GitHub

How to install create-epic?

aleksander-dytko/ai-pm-workspace/create-epic

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill create-epic

Installs into the current project.

Summary

Turn an idea into a structured epic draft using templates/epic-template.md

Files · 1

View on GitHub

SKILL.md

1	# Create Epic
2
3	You help turn a raw product idea into a well-structured epic draft. The output follows `templates/epic-template.md` and lands in `epics/` with `stage: Explore`.
4
5	## Input
6
7	The user provides via `$ARGUMENTS`:
8	- A short prompt (e.g., "unified onboarding dashboard for CSMs"), OR
9	- A path to a raw idea note (e.g., `samples/sample-epic-idea.md`)
10
11	## Workflow
12
13	### 1. Gather context
14
15	Read the raw idea. If `$ARGUMENTS` is a path, read that file. Otherwise use the prompt directly.
16
17	Read supporting context in parallel:
18	- `templates/epic-template.md` - the target structure
19	- `docs/epic-lifecycle.md` - the stage framework
20	- `research/personas/` - personas that might match the target user
21	- `Dashboard/people-profiles.md` - any stakeholders mentioned
22	- `Loose Notes/Work/` and `Meetings/` - related prior discussions (search by keywords from the idea)
23	- `Initiatives/` - does this fit under an existing initiative?
24
25	### 2. Identify gaps in the idea
26
27	Before drafting, identify what's missing or unclear. Ask the user 3-5 focused questions in ONE `AskUserQuestion` round if any of these are unclear from the raw input:
28
29	- Target user: which persona does this serve? (Offer personas from `research/personas/` as options.)
30	- Primary metric: what measurable outcome should improve?
31	- Scope boundary: what is explicitly NOT in this epic?
32	- Initiative fit: does this belong under an existing initiative (show list from `Initiatives/`) or does it stand alone?
33	- Competitor check: has competitive research been done? (Offer `/competitive-research` if not.)
34
35	Skip questions where the raw idea already has a clear answer. Maximum one round.
36
37	### 3. Draft the epic
38
39	Use `templates/epic-template.md` as the structure. Fill what you can from the raw idea + answers:
40
41	Required sections (always fill):
42	- Value Proposition Statement - one crisp statement of the outcome.
43	- User Problem - 1-2 paragraphs from the customer's perspective. Frame from the "why", not the product's failure.
44	- User Stories - 3-6 stories at the "what" level (Explore phase). Add the "how" later.
45
46	Phase-specific (fill lightly in Explore, flag for Scope):
47	- Breakdown - list sub-activities under Explore (customer interviews, research, opportunity-solution tree).
48	- Risk Assessment - initial class only, full in Scope.
49
50	Skip for now:
51	- Release Notes (drafted in Scope or later).
52	- Implementation Notes (Scope phase).
53	- Design Planning, Documentation Planning (Scope phase).
54	- Validation Criteria (Validate phase).
55
56	Fill placeholders honestly. If you don't know something, write `[To determine during Scope]` or `[Needs user research]`. Don't fabricate.
57
58	### 4. File location and naming
59
60	- Folder: `epics/`. Create if it doesn't exist.
61	- Filename: `YYYY-MM-DD - [Epic Title slug].md`. Example: `2026-04-20 - Unified onboarding dashboard.md`.
62	- Frontmatter: set `stage: Explore`, `status: exploring`, `created: YYYY-MM-DD`.
63
64	### 5. Link the epic
65
66	- Daily journal: add a link in today's journal under `## Notes`. Format: `- [[YYYY-MM-DD - Epic Title]] - new epic in Explore stage`.
67	- Initiative: if the epic fits under an existing initiative (from step 2), add a link in the initiative file under `## Epics under this initiative`.
68	- Nothing external: do NOT push to any external tracker. The epic lives in the vault until you explicitly ship it elsewhere.
69
70	### 6. Propose follow-up tasks
71
72	Based on what's missing in the draft, propose 2-5 tasks that would move the epic out of Explore. Examples:
73
74	- Schedule 5 customer interviews with target persona
75	- Run `/competitive-research` on [topic]
76	- Run `/opportunity-solution-tree` for the primary metric
77	- Review the draft with [stakeholder]
78	- Draft a 3-bullet research brief for the user research team
79
80	Show the proposed task list and wait for user confirmation. After confirmation, append to `Dashboard/tasks.md` under "This week" with format:
81
82	```
83	- [ ] Task - source: [[YYYY-MM-DD - Epic Title]] - due: YYYY-MM-DD - priority: P3
84	```
85
86	### 7. Output summary
87
88	```
89	✅ Epic drafted: [[YYYY-MM-DD - Epic Title]]
90	✅ Linked in today's journal
91	[if initiative match] ✅ Linked under [[Initiative]]
92
93	Stage: Explore
94	Status: exploring
95
96	📋 Proposed follow-up tasks (to move to Scope):
97	1. [Task]
98	2. [Task]
99
100	Confirm: Add tasks to Dashboard/tasks.md? (Y/N)
101
102	💡 Next steps in the lifecycle: see docs/epic-lifecycle.md
103	```
104
105	## Notes
106
107	- Honesty over completeness. It's better to mark a section as `[Needs user research]` than to invent answers.
108	- Epics start thin and grow. The Explore-stage draft should be under 1 page. Sections get filled as the epic progresses.
109	- One initiative per epic. If the idea fits under multiple initiatives, flag this as a scope problem rather than dual-linking.
110	- **User stories f

People who liked this also viewed

6 picks

Type