xiduzo/wtf / skills/wtf.epic-to-features
wtf.epic-to-features
VerifiedThis skill should be used when a user wants to decompose an Epic into its complete set of Features all at once, invoked automatically after write-epic completes, or triggered by phrases like "create all features for this epic", "walk me through all the features", "let's break down this epic", or "plan the features for epic
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| evals/evals.json | config | 3.8 KB |
| evals/fixtures/existing-features-epic.json | config | 1.7 KB |
| evals/fixtures/multi-actor-epic.json | config | 1.5 KB |
| evals/fixtures/ordered-capabilities-epic.json | config | 1.5 KB |
evals/fixtures/multi-actor-epic.json
View on GitHub{
"_note": "Fixture for eval 1 — Epic with two distinct domain actors (Merchant, Finance Manager) and no existing Features. Tests that the skill proposes at least one Feature per actor and that all proposed Features follow the [Actor] can [verb] [object] pattern without implementation vocabulary.",
"epic": {
"number": 1,
"title": "Epic: Settlement Management Platform",
"labels": [{ "name": "epic" }],
"body": "## Goal\nMerchants can track, filter, and export their settlement history. Finance Managers can generate consolidated reports across all merchants and flag anomalies.\n\n## Context\nThe settlement domain currently has no self-service visibility. Merchants open support tickets to query settlement status. Finance Managers use spreadsheet exports manually assembled from the payments database. Both workflows are slow, error-prone, and do not scale.\n\n## Domain Actors\n- **Merchant** — a business receiving payouts from the platform\n- **Finance Manager** — an internal operator responsible for cross-merchant financial oversight\n\n## Success Metrics\n- Merchant can view real-time settlement status for any completed payment\n- Merchant can filter their settlement history by date range\n- Finance Manager can export a cross-merchant settlement report\n- System notifies Merchant when a settlement is delayed beyond the expected window\n- Finance Manager can flag anomalous settlements for review\n\n## Bounded Context\nSettlement"
},
"existing_features": []
}
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 | Unverified | 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 |