work-next-issue-in-given-epic

Select and complete the next actionable child issue from a GitHub EPIC.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/waywarden --skill work-next-issue-in-given-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-next-issue-in-given-epic
Source: https://github.com/marcmontecalvo/waywarden/tree/main/.agents/skills/work-next-issue-in-given-epic
Command: npx skills add https://github.com/marcmontecalvo/waywarden --skill work-next-issue-in-given-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Waywarden teams often struggle to manually shepherd EPICs into concrete work items. This Skill autonomously identifies and executes the next actionable child issue from a GitHub EPIC, ensuring progress and traceability.

Core Features & Use Cases

  • Autonomous EPIC scoping and next-issue selection
  • End-to-end workflow execution: branch creation, baseline checks, tests, review, merge, and post-merge verification
  • Adversarial review and formal validation to ensure acceptance criteria are proven

Quick Start

Provide a GitHub EPIC URL and the current repo state, and command this skill to execute the next actionable child issue end-to-end.

Frequently Asked Questions about work-next-issue-in-given-epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the execution of the next actionable issue from a GitHub epic?

To automate GitHub epic execution, provide the epic URL and local working tree to enable autonomous selection, branch creation, testing, adversarial review, and merge into main with post-merge verification.

What is an end-to-end epic workflow with automated issue selection?

An end-to-end epic workflow autonomously scopes child issues from a provided epic URL, executing branch creation, baseline checks, tests, pre-commit gates, and formal validation to ensure acceptance criteria are proven.

How to enforce pre-commit gates and adversarial review when completing epic issues?

Enforce pre-commit gates and adversarial review by applying automated issue execution that validates baseline checks, runs tests, and proves acceptance criteria prior to merging into the main branch.

Does automated issue execution work with my local working tree and GitHub issue bodies?

Automated issue execution works with your local working tree and GitHub issue bodies by consuming the provided epic URL, issue comments, and linked docs to guide scoping and full validation.

What is the best way to ensure traceability when advancing child issues in an epic?

The best way to ensure epic traceability is autonomous end-to-end execution that selects the next actionable child issue, applies formal validation, merges into main, and runs post-merge verification.

When should I not use automated epic workflows for issue completion?

Avoid automated epic workflows when manual scoping is required or when the local working tree, issue bodies, and linked docs are unavailable to guide baseline checks, tests, and pre-commit gates.