wtf.loop

Automate Epic or Feature execution by chaining implement, verify, and PR tasks.

7|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wtf.loop
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.loop
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates end-to-end execution of a fully specified Epic or Feature by chaining implement → verify → PR, enforcing dependency order and human-in-the-loop gates to prevent drift and ambiguities.

Core Features & Use Cases

  • Builds a unified dependency graph across Epics, Features, and Tasks, including external blockers, and plans execution in phases with conflict-aware sub-phases for parallel work.
  • Spawns and coordinates sub-agents to implement tasks, verify outcomes, and create PRs while surfacing unresolved questions for human input.
  • Enforces pre-conditions (e.g., designed labels, complete Gherkin contracts, non-empty acceptance criteria) before execution and ensures PRs are merged in sequence as gates progress.

Quick Start

Approve a target Epic or Feature and the proposed execution plan, then allow the loop to execute tasks in phases with human-in-the-loop gates.

Frequently Asked Questions about wtf.loop

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

FAQPage Schema
How do I automate Epic and Feature execution end-to-end in GitHub Issues?▼

Automating Epic and Feature execution requires chaining implement, verify, and PR creation steps in dependency order. This loop orchestrates sub-agents to handle tasks autonomously while enforcing human-in-the-loop gates to prevent drift across your task hierarchy.

What is topological execution planning for software features?▼

Topological execution planning builds a unified dependency graph across Epics, Features, and Tasks to schedule execution in phases. It organizes work into conflict-aware sub-phases, allowing parallel execution while respecting external blockers and dependency order.

How do I manage CI gate handling and PR merges for automated task execution?▼

CI gate handling ensures PRs are merged in sequence as phases progress. The loop coordinates sub-agents to create PRs and manages CI gates automatically, surfacing unresolved questions or external blockers for human input before proceeding.

Do I need Gherkin contracts and acceptance criteria before automating feature implementation?▼

Yes, Gherkin contracts and non-empty acceptance criteria are mandatory pre-conditions. The loop enforces pre-flight checks requiring complete contracts and designed labels before executing tasks to ensure the feature is fully specified.

What's the best way to handle unresolved questions during autonomous Epic execution?▼

Handling unresolved questions during autonomous execution relies on targeted human-in-the-loop gates. The loop surfaces specific questions and external blockers for human review at phase boundaries, preventing ambiguous implementations from propagating downstream.

When should I not use autonomous task orchestration for GitHub Issues?▼

You should avoid autonomous task orchestration when Epics or Features lack full specification, such as missing Gherkin contracts or acceptance criteria. The loop's pre-flight checks will block execution if pre-conditions are unmet or external blockers remain unresolved.