Add harness-epic skill for epic-level roadmaps#1
Open
eliknebel wants to merge 2 commits into
Open
Conversation
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.
Adds a new
harness-epicskill for creating or updating epic-level roadmap documents from informal source material.This skill is intended for epics composed of multiple feature slices, where the desired output is a parent
plan.mdthat sequences child work items rather than a phase-by-phase implementation plan for one feature.Added
skills/epic/SKILL.mdskills/epic/references/roadmap_guidance.mdskills/epic/assets/templates/epic_plan_template.mdUsage
Use
harness-epicwhen an epic has aninformal.mdor similar source document and needs a high-level roadmap that:harness-analyze,harness-architect,harness-requirements, andharness-planNotes
This intentionally does not replace
harness-plan;harness-planremains the right tool for implementation planning once a single child feature has PRD/FDD artifacts.