Chunk an RFC into an Epic and sub-issues, then execute a branch-to-merge loop per chunk.
npx skills add https://github.com/enkira-ai/claude-plugins --skill rfc-loop
Please help me install this Agent Skill. Skill: rfc-loop Source: https://github.com/enkira-ai/claude-plugins/tree/main/plugins/rfc-loop/skills/rfc-loop Command: npx skills add https://github.com/enkira-ai/claude-plugins --skill rfc-loop
Helps engineering teams convert merged RFCs into shipped code by dividing the work into a single Epic plus N sub-issues and guiding a deterministic land-and-review loop across PRs, reviews, and merges until the RFC is landed. This approach ensures traceability, staged reviews, and a final completion report that closes the Epic.
Start by loading the plan and the target RFC, then trigger the first held implementer to begin chunk 1.
High-intent search queries and answers about installing and using this skill.
Automating RFC-to-PR workflows involves chunking an RFC into an Epic with sub-issues, then running a branch, PR, review, and merge loop sequentially. This staged approach ensures traceability and closes the Epic automatically after all chunks land.
Breaking down a large RFC for incremental code review requires splitting it into an Epic plus N sub-issues. You then develop, review, and merge each chunk individually before proceeding, culminating in a final RFC completion report.
Yes, you can enforce test-driven commits and spec reviews in a multi-PR RFC landing. The workflow enforces a plan-driven lifecycle with subagent implementers and a dedicated spec-review step before merging each chunk.
Maintaining RFC traceability across multiple Git workflow chunks is achieved by using RFC-traceable trailers on commits. This connects each merged PR back to the original Epic, ensuring the sub-issue chunks align with the broader specification.
No, you do not need a pre-existing Epic to start automating RFC code reviews. The process initializes by loading the target RFC and automatically chunking it into a single Epic plus N sub-issues before triggering the first implementer.
You should avoid executing an RFC-to-code branch and merge loop for single-PR changes or trivial updates that do not require multi-PR RFC landings. This approach is designed for complex workloads needing staged reviews and spec-driven traceability.
zoonkConvert implementation plans into GitHub epics with sub-issues and dependencies.
pkuppensMerge approved pull requests into main and delete source branches.
NeoLabs-SystemsDispatch fresh subagents for task execution and two-stage code review.
RaphaelSilvaOrchestrate ArenaQuest task execution, branch topology, and PR creation.
