xiduzo/wtf / skills/wtf.health
wtf.health
VerifiedThis skill should be used when a developer or lead wants a project status overview — what is blocked, stale, unverified, or waiting on a next step — for example "project health check", "what's blocking the release", "standup summary", or "what's left in this epic". Scans all open WTF issues — Traces plus legacy Tasks — and produces a triage-ready health report with actionable next steps.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.5 KB |
| evals/evals.json | config | 4.5 KB |
| evals/fixtures/clean.json | config | 230 B |
| evals/fixtures/implemented-not-verified.json | config | 1.6 KB |
| evals/fixtures/legacy-task-and-unticked-plan.json | config | 2.4 KB |
| evals/fixtures/stale-designed.json | config | 1.7 KB |
evals/fixtures/legacy-task-and-unticked-plan.json
View on GitHub{
"_note": "Fixture for eval 4 — a migrated repo. `tasks` holds one legacy task-labeled issue (#33) that no Trace Plan entry names. `traces` holds #42, labeled verified with a merged PR, but its Trace Plan entry in Feature #10 is still `[ ]` — the plan is out of sync with the labels. Arrays match gh issue list --json number,title,labels,updatedAt output; features also carry body; pull_requests carry state.",
"epics": [
{
"number": 5,
"title": "🎯 Settlement Visibility",
"labels": [
{
"name": "epic"
}
],
"updatedAt": "2026-05-01T09:00:00Z"
}
],
"features": [
{
"number": 10,
"title": "🚀 Merchant can view settlement status for a completed payment",
"labels": [
{
"name": "feature"
},
{
"name": "designed"
}
],
"updatedAt": "2026-05-01T10:00:00Z",
"body": "## User Stories\n\n### Story: Merchant sees settlement status\nAs a Merchant, I want to see the settlement status of a completed payment, so that I can track my payout.\n\n```gherkin\nScenario: Status shown for a settled payment\n Given a Merchant has a completed payment that is settled\n When the Merchant opens the payment detail page\n Then the settlement status 'Settled' is shown\n```\n\n## Trace Plan\n\n1. [ ] ☄️ Skeleton — Merchant sees settlement status for one completed payment (claims: \"Status shown for a settled payment\") #42"
}
],
"traces": [
{
"number": 42,
"title": "☄️ Skeleton — Merchant sees settlement status for one completed payment",
"labels": [
{
"name": "trace"
},
{
"name": "designed"
},
{
"name": "implemented"
},
{
"name": "verified"
}
],
"updatedAt": "2026-05-03T14:30:00Z"
}
],
"tasks": [
{
"number": 33,
"title": "🛠 Task: Seed settlement fixtures for staging",
"labels": [
{
"name": "task"
},
{
"name": "designed"
},
{
"name": "implemented"
}
],
"updatedAt": "2026-05-02T11:00:00Z"
}
],
"bugs": [],
"pull_requests": [
{
"number": 7,
"title": "feat(settlement): show status for a settled payment",
"headRefName": "trace/42-settlement-status",
"body": "Closes #42",
"state": "MERGED"
}
]
}
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: 472k | 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: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |