feat(skills/product-epic): add standalone epic-scoping skill#19
Merged
Conversation
Adds a standalone skill that takes a rough product epic and drives it to readiness for engineering: it proves readiness with isolated fresh-reader subagents (engineer + stakeholder) rather than self-assessment, refuses to write unconfirmed assumptions as fact, and lands the result via writing-github-issues. Sits upstream of planning-a-feature; nothing in the feature flow routes into it, so it is documented in the README table only, matching the existing convention for standalone skills. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
New skill (product-epic) is an additive feature; minor bump. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
product-epic, a standalone skill that takes whatever a product manager has — a rough idea, a few bullets, an early draft — and drives it to an epic an engineer can design against. It sits upstream ofplanning-a-feature; nothing in the feature-development flow routes into it, and it routes into nothing exceptwriting-github-issuesto land the result.The skill exists because "is this epic ready?" is the wrong question to answer by re-reading your own draft — you hold the whole idea in your head, so it always reads clear. This skill makes readiness something a fresh reader proves, not something the author asserts.
Changes
skills/product-epic/SKILL.mdand itstemplates/product-epic.mdepic template.## Open confirmationsitem), and the scope-vs-usability cut is the PM's call to make and the skill's job to record, not invent.drafting-a-release); theproject-CLAUDE.mdflow diagram is intentionally left unchanged.Testing
Dogfooded end-to-end this session against a real, messy product epic. The skill caught a direct contradiction between the value proposition and the implementation notes, surfaced unsubstantiated SLA/RTO numbers being passed off as fact, and — after a refinement pass — a second isolated fresh-engineer reader confirmed zero surprise blockers remained, with every unknown either resolved or filed as an owned confirmation. The fresh-reader isolation (subagents given only the epic text) behaved as designed: they found gaps the author's own read had glossed.