Skip to content

xiduzo/wtf / skills/wtf.health

wtf.health

Verified

This 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.

evals/fixtures/stale-designed.json

View on GitHub
{
  "_note": "Fixture for eval 3 — one trace stale (designed but not implemented for well over 7 days). updatedAt is 2025-01-01 so the trace is always stale regardless of when the eval runs. Arrays match gh issue list --json number,title,labels,updatedAt output; features also carry body (User Stories + Trace Plan). The Trace Plan claims all scenarios, so no Skeleton or partition-gap finding fires.",
  "epics": [
    {
      "number": 5,
      "title": "🎯 Settlement Visibility",
      "labels": [{"name": "epic"}],
      "updatedAt": "2025-01-01T09:00:00Z"
    }
  ],
  "features": [
    {
      "number": 10,
      "title": "🚀 Merchant can view settlement status in merchant dashboard",
      "labels": [{"name": "feature"}, {"name": "designed"}],
      "updatedAt": "2025-01-01T09:00:00Z",
      "body": "## User Stories\n\n### Story: Merchant sees settlement status in the dashboard\nAs a Merchant, I want to see settlement status in the merchant dashboard, so that I can track payouts without contacting support.\n\n```gherkin\nScenario: Settlement status shown in the merchant dashboard\n  Given a Merchant has settlements\n  When the Merchant opens the merchant dashboard\n  Then each settlement shows its settlement status\n```\n\n## Trace Plan\n\n1. [ ] ☄️ Skeleton — Merchant sees settlement status in the merchant dashboard (claims: \"Settlement status shown in the merchant dashboard\")"
    }
  ],
  "traces": [
    {
      "number": 17,
      "title": "☄️ Skeleton — Merchant sees settlement status in the merchant dashboard",
      "labels": [{"name": "trace"}, {"name": "designed"}],
      "updatedAt": "2025-01-01T10:00:00Z"
    }
  ],
  "bugs": [],
  "pull_requests": []
}
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall