feat: add epic sequence implementation skill - #2
Merged
Conversation
shaug
marked this pull request as ready for review
July 19, 2026 23:35
- Add an end-to-end workflow for implementing GitHub and Linear epics - Encode bounded adversarial and connector review gates - Preserve current-candidate validation, safe merge, and cleanup requirements - Make the established ticket implementation workflow reusable across projects - Keep dependency ordering, review evidence, and mutation authority explicit
shaug
force-pushed
the
scott/add-implement-epic-sequence-skill
branch
from
July 20, 2026 01:27
c83d72b to
06bd81f
Compare
14 tasks
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
Adds a reusable skill for executing GitHub- or Linear-owned epic sequences through live dependency selection, focused implementation, current-candidate review gates, safe merge, and conservative closeout.
Summary
This introduces an end-to-end epic implementation workflow built around the operating patterns used across the project portfolio. It selects work from live native dependency graphs, keeps each child ticket isolated to one branch and pull request, and distinguishes issue-tracker ownership from pull-request hosting.
The workflow makes mutation authority explicit before execution and carries candidate identity through validation, adversarial review, human approval, connector review, and merge. Connector handling covers automatic and request-driven initiation, accepted current-head signals, complete feedback disposition, bounded polling and feedback cycles, and fail-closed behavior when evidence is missing.
The skill also codifies clean-candidate requirements, base-drift invalidation, read-only reviewer integrity checks, safe branch and worktree cleanup, late-feedback sweeps, and evidence-based epic closure. GitHub, Linear, review, merge, and cleanup details are separated into focused references so agents load only the guidance relevant to the active workflow.