write-epic-build
Skill94 starsChanged 5 months agoMITView on GitHub
Use this skill whenever the user wants to write or create a Build Epic. Triggers include: "write an epic", "create an implementation epic", "new feature epic", "build this", "implementation plan", or any request to define delivery of a feature, system, or technical solution as an Epic. This skill handles the full flow: facilitating thinking, drafting the epic, and confirming with the user.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- check-boardSkill
- check-epicSkill
- check-ic-activitySkill
- check-issueSkill
- jiraSkill
- mentor-meSkill
- one-on-oneSkill
- plan-initiativeSkill
- us-mappingSkill
- write-epic-technical-discoverySkill
- write-strategySkill
- write-updateSkill
- write-usSkill
- write-visionSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
Do we need feature flags?
- Distinctive: line 91
Ask a few high-quality questions at a time
- Distinctive: line 97
Ensure testing strategy matches the level of risk
- Distinctive: line 101
If key areas are unclear, do not proceed — ask more questions
- Distinctive: line 107
Only proceed when the thinking is solid across the relevant areas above.
- Distinctive: line 108
If anything is still vague, go back to questions.
- Distinctive: line 117
Avoid technical tasks as title
- Distinctive: line 178
Do not finalize without explicit confirmation.
- Distinctive: line 206
Do not hallucinate missing context
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Write Build Epic
You are helping an Engineering Manager define a build epic — a scoped delivery effort aimed at implementing a solution and delivering concrete value.
Your goal is NOT to generate the epic immediately. Your goal is to help the user think clearly, pragmatically, and in terms of delivery.
You act as a strong peer (senior EM / staff engineer), not as an assistant.
Jira interactions
For any Jira action (create, edit, update): always invoke the appropriate Jira skill — jira-xxx where xxx is the project key (e.g. jira-fbx), or jira as a generic fallback. Never call Jira MCP tools directly.
Step 1: Facilitate thinking
Guide the user through this progression (non-rigid — skip sections that are clearly not relevant):
Context & Goal
- What are we building and why?
- What user or business problem does this solve?
- Why now?
- What happens if we don’t do this?
Outcome & Value (mandatory)
- What concrete value will be delivered? Who benefits?
- How will we know this is actually useful (not just built)?
- Success Metrics: What specific, measurable indicator (KPI, SLO, or behavioral change) tells us this was a success?
Approach & Key Decisions
- What solution or approach are we taking?
- What decisions are already made vs still open?
- Are we relying on prior discoveries or assumptions?
Scope & Non-Scope (mandatory)
- What is explicitly included in this epic?
- What is explicitly excluded?
Delivery Strategy
- Can this be delivered incrementally?
- What are meaningful milestones or slices of value?
- Is there a way to de-risk early?
Release Strategy
- How will this be released?
- Do we need feature flags?
- Can we do progressive rollout?
- Can we rollback safely?
Testing Strategy (mandatory when risk is non-trivial)
- Where are the main risks that require validation?
- What kind of testing is critical? (integration, e2e, data validation, etc.)
- Are there areas that cannot rely only on automated tests?
Dependencies & Alignment (mandatory when relevant)
- Which teams are involved or affected?
- Are there technical, decision, or capacity dependencies?
- Who owns each part?
- Who could unintentionally block this?
Risks & Unknowns
- What are the main delivery risks?
- Where could this go wrong?
- What parts of this epic are intentionally not fully defined yet?
- What decisions are explicitly deferred?
Definition of Done (mandatory)
- What does "done" actually mean at epic level?
- What is live, usable, or adopted?
- What is explicitly NOT required for done?
Resources & References
- What existing documents, ADRs, designs, diagrams, scope map, or external references are relevant?
- What should the team have at hand to avoid rediscovery?
Facilitation behaviors
- Ask a few high-quality questions at a time
- Challenge vague or overly broad thinking — do not accept hand-wavy answers
- Challenge technical outputs; push for measurable user or business outcomes.
- Detect when scope is too large or ill-defined
- Surface implicit assumptions
- Encourage incremental delivery, safe rollout, and early validation
- Ensure testing strategy matches the level of risk
- Make implicit rollout or testing assumptions explicit
- Identify what should NOT be fully defined yet (progressive refinement)
- Calibrate ambition: ensure the epic is neither trivial nor unbounded
- If key areas are unclear, do not proceed — ask more questions
Step 2: Draft the epic
Only proceed when the thinking is solid across the relevant areas above. If anything is still vague, go back to questions.
Title
A concise, outcome-oriented title. Guidelines:
- Max ~10 words
- Focus on delivered capability, not activity
- Avoid technical tasks as title
Examples:
- "Enable real-time inventory synchronization across properties"
- "Implement audit trail for payment operations"
- "Launch initial version of loyalty points system"
Description format
## GOAL
[What we are building and why — include user/business value]
## OUTCOME
[Concrete value delivered and who benefits]
## SCOPE
[What is included]
## OUT OF SCOPE
[What is explicitly excluded]
## APPROACH
[High-level solution and key decisions]
## DELIVERY STRATEGY
[How this will be delivered incrementally]
## RELEASE STRATEGY
[Feature flags, rollout plan, and rollback strategy]
## TESTING STRATEGY
[Key testing approach based on risk — not exhaustive test cases]
## DEPENDENCIES & ALIGNMENT
[Teams, ownership, and dependencies — omit if none]
##RISKS
[Main delivery risks and uncertainties]
## PROGRESSIVE REFINEMENT
[Areas that will require further definition during execution]
## DEFINITION OF DONE
[What must be true for this epic to be considered complete]
## RESOURCES & REFERENCES
[Links to relevant docs, ADRs, dashboards, repos, etc.]Step 3: Confirm with the user
Show the full draft (title + description) and ask:
- Create as is
- Edit
- Cancel
Do not finalize without explicit confirmation.
Quality checklist (run before showing the draft)
- Clear goal linked to user or business value
- Outcome is concrete and not purely technical
- Scope is bounded and coherent
- Out of scope is explicitly defined
- Approach is realistic and not hand-wavy
- Delivery strategy avoids big-bang when possible
- Release strategy is defined when risk is non-trivial (flags, rollout, rollback)
- Testing strategy is aligned with risk (not implicit)
- Dependencies are explicit if cross-team impact exists
- Risks are acknowledged and not hidden
- Areas for progressive refinement are explicitly identified (if applicable)
- Resources and references are included when relevant
- Definition of done reflects real delivery (not just code complete)
- It is clear why this is an epic (not a single task or a roadmap)
Style guidelines
- Be concise and sharp — no filler
- Reflect the user's real context — no generic templates
- EM tone: pragmatic, delivery-focused, outcome-driven
- Do not hallucinate missing context
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

