work-entire-epic

Automates completing all open actionable GitHub EPIC child issues via the repo-local next-issue workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the completion of every open actionable child issue within a GitHub EPIC by repeatedly invoking the repo-local work-next-issue-in-given-epic workflow, ensuring progress until completion or blockage.

Core Features & Use Cases

  • Orchestrates end-to-end EPIC completion by iterating through actionable child issues in order, honoring dependencies and blockers.
  • Reuses the repo-local next-issue workflow to maintain consistency with project conventions.
  • Provides clear progress updates and enforces standard validation gates before commits.

Quick Start

Provide the EPIC identifier (number, name, or URL) to start automatically completing all open actionable child issues.

Frequently Asked Questions about work-entire-epic

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

FAQPage Schema
How do I automate completing all child issues within a GitHub EPIC?

To automate GitHub EPIC completion, provide an EPIC identifier (number, name, or URL) and the workflow iterates through actionable child issues, committing to main with tests until completion or blockage.

What happens when the automated EPIC workflow encounters a blocked child issue?

When a blocked child issue is encountered during EPIC automation, the workflow halts processing and stops iterating, ensuring no dependent issues are attempted before their blockers are resolved.

Does the automated EPIC workflow respect issue dependencies and sequencing?

Yes, the automated EPIC workflow respects dependencies and sequencing notes, enforcing strict validation gates before commits to ensure child issues are completed in the correct order.

Can I reference a GitHub EPIC by name or URL instead of just an issue number?

Yes, you can reference a GitHub EPIC by issue number, name, or direct GitHub URL; the workflow accepts all three identifier formats to start automating child issue completion.

What is the best way to ensure commits follow standard formatting during EPIC automation?

The best way to ensure standard commit formatting during EPIC automation is to use the built-in validation gates, which enforce standard commit formats and run tests after each completed child issue.

Do I need a specific repo-local workflow installed to automate end-to-end EPIC completion?

Yes, you need the repo-local work-next-issue-in-given-epic workflow installed, as the automation repeatedly invokes it to maintain consistency with project conventions while completing child issues.