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/linear-chain.json
View on GitHub{
"_note": "Spine-first chain: one Feature with three Traces in Trace Plan order — Skeleton #10, then #11, then #12. No dependency edges exist. Every Trace declares `## Impacted Areas` that overlap on src/settlements/status/, so the intra-Feature conflict graph serializes them. Expected: one Feature unit whose Traces run strictly sequentially in plan order, no parallelism.",
"feature": {
"number": 1,
"title": "Feature: Settlement status",
"labels": [
"feature"
],
"body": "## Goal\nMerchants can see the settlement status of a completed payment.\n\n## Acceptance Criteria\n- [ ] Merchants can see the status of a settled payment\n- [ ] Merchants can see why a settlement failed\n- [ ] Merchants can see that a settlement is pending\n\n## User Stories\n### Story: Merchant sees settlement status\nAs a Merchant, I want to see the settlement status of a payment, so that I know when funds arrive.\n\n```gherkin\nScenario: Status shown for a settled payment\n Given a Merchant has a settled payment\n When the Merchant opens the settlement list\n Then the payment shows status 'settled'\n\nScenario: Status for a failed settlement\n Given a Merchant has a failed settlement\n When the Merchant opens the settlement list\n Then the payment shows status 'failed' with a reason code\n\nScenario: Status while settlement is pending\n Given a Merchant has a pending settlement\n When the Merchant opens the settlement list\n Then the payment shows status 'pending'\n```\n\n## Trace Plan\n1. [ ] ☄️ #10 Skeleton — status for one settled payment (claims: \"Status shown for a settled payment\")\n2. [ ] ☄️ #11 Deepening — failed settlement (claims: \"Status for a failed settlement\")\n3. [ ] ☄️ #12 Deepening — pending settlement (claims: \"Status while settlement is pending\")\n\n## Impacted Areas\n- src/settlements/"
},
"nodes": [
{
"number": 10,
"title": "Trace: Skeleton — status for one settled payment",
"type": "trace",
"labels": [
"trace",
"designed"
],
"feature": 1,
"body": "## Spine Position\n- Position: Skeleton\n- Builds on: none\n\n## Impacted Areas\n- Backend: src/settlements/status/StatusService.ts\n- Frontend: src/ui/SettlementList.tsx\n- Database: —\n- APIs: GET /settlements\n- External systems: —"
},
{
"number": 11,
"title": "Trace: Deepening — failed settlement",
"type": "trace",
"labels": [
"trace",
"designed"
],
"feature": 1,
"body": "## Spine Position\n- Position: Deepening\n- Builds on: Trace #10\n\n## Impacted Areas\n- Backend: src/settlements/status/StatusService.ts\n- Frontend: src/ui/SettlementList.tsx\n- Database: —\n- APIs: GET /settlements\n- External systems: —"
},
{
"number": 12,
"title": "Trace: Deepening — pending settlement",
"type": "trace",
"labels": [
"trace",
"designed"
],
"feature": 1,
"body": "## Spine Position\n- Position: Deepening\n- Builds on: Trace #11\n\n## Impacted Areas\n- Backend: src/settlements/status/StatusService.ts\n- Frontend: src/ui/SettlementList.tsx\n- Database: —\n- APIs: GET /settlements\n- External systems: —"
}
],
"edges": {
"10": {
"blocks": [],
"blocked_by": []
},
"11": {
"blocks": [],
"blocked_by": []
},
"12": {
"blocks": [],
"blocked_by": []
}
}
}
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 |