Make ticket and epic execution runtime agnostic - #22
Merged
Conversation
## Summary - Define product-neutral runtime capabilities for ticket and epic execution - Document the stable implement-epic to implement-ticket to review-code-change chain - Add compatible-context and missing-capability evaluation profiles ## Why - Let capable agent runtimes execute the composed workflow without a Codex-only API - Fail closed when required review, isolation, or asynchronous waiting is unavailable - Preserve the established ticket, review, merge, graph, and closeout boundaries
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
Makes
implement-ticketandimplement-epicportable across capable agent runtimes while preserving their existing execution, review, merge, and closeout guarantees.Summary
implement-epicthroughimplement-ticketto repository-ownedreview-code-change.agents/are optional discovery metadata rather than part of the portable contracts.Why
The workflow depends on capabilities—isolated mutation, fresh read-only review, structured tracker access, asynchronous gate monitoring, and verifiable terminal evidence—not on a particular agent product or API name. Making those requirements explicit lets other capable runtimes implement the same safeguards without adding a compatibility framework or duplicating ticket behavior inside the epic orchestrator.
Validation
just formatjust lintjust test— 107 tests passedjust test-implement-ticket— 12 tests passedjust test-implement-epic— 12 tests passedTickets
Fixes #11