Replace implement-epic-sequence with implement-epic - #21
Merged
Conversation
## Summary - Replace `implement-epic-sequence` with the canonical `implement-epic` skill - Delegate one-ticket execution and review mechanics to `implement-ticket` - Add focused graph, result, authority, closeout, and forward-evaluation contracts ## Why - Keep epic orchestration focused on live dependency selection and refresh - Establish one canonical owner for ticket implementation, review, merge, and cleanup - Preserve scope and authority boundaries while allowing future safe parallel execution
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
1 participant
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.
TL;DR
Replaces
implement-epic-sequencewith a smallerimplement-epicorchestrator that delegates every selected child to the canonicalimplement-ticketworkflow.Summary
implement-epicand remove the unsupported former name after confirming there are no repository-owned compatibility consumers.implement-ticketinvocation per selected child, terminal-result verification, graph refresh, and separately authorized closeout.implement-ticket.Why
The prior skill duplicated the single-ticket workflow and encoded its graph-walking strategy in the public name. This composition creates one canonical execution layer, makes the epic contract easier to audit, and preserves dependency and authority gates without introducing a workflow framework or compatibility alias.
Validation
just formatjust lintjust testjust test-implement-epicjust test-implement-ticketskills/implement-epicTickets
Fixes #19