xiduzo/wtf / skills/wtf.loop
wtf.loop
VerifiedThis skill should be used when a developer wants to autonomously execute all Traces under a fully-specified Epic or Feature — for example "go", "start building", "implement everything", "run the loop", "execute the feature", "build it all", "kick it off". Requires that the Epic/Feature/Trace tree is fully written before starting. Chains implement → verify → PR → re-aim for every Trace — spine-first within each Feature, parallel across Features — with targeted human-in-the-loop gates for contradictions, ambiguities, and every change to a Trace Plan's scenario set.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.5 KB |
| evals/evals.json | config | 10.8 KB |
| evals/fixtures/contradiction-spec.json | config | 3.0 KB |
| evals/fixtures/diamond-file-conflict.json | config | 2.3 KB |
| evals/fixtures/external-blocker.json | config | 863 B |
| evals/fixtures/linear-chain.json | config | 3.4 KB |
| evals/fixtures/parallel-features.json | config | 1.6 KB |
| evals/fixtures/sibling-traces-parallel.json | config | 5.2 KB |
| evals/fixtures/trunk-delivery-close.json | config | 2.9 KB |
| references/pre-flight-validation.md | markdown | 6.9 KB |
| references/trace-execution.md | markdown | 14.2 KB |
evals/fixtures/external-blocker.json
View on GitHub{
"_note": "Feature #40 has a blocked_by edge pointing to issue #999, which is not in the node list. Feature #41 is blocked by #40. Step 2d should classify #999 as an external blocker, surface it in the pre-flight gate, and not proceed to step 3 until the external dependency is resolved. Trace Plans are omitted — only dependency validation (2d) runs in this eval.",
"nodes": [
{
"number": 40,
"title": "Feature: Settlement retry",
"type": "feature",
"labels": ["feature"],
"impacted_areas": ["src/settlements/retry/"]
},
{
"number": 41,
"title": "Feature: Retry notifications",
"type": "feature",
"labels": ["feature"],
"impacted_areas": ["src/notifications/"]
}
],
"edges": {
"40": {"blocks": [], "blocked_by": [999]},
"41": {"blocks": [], "blocked_by": [40]}
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |