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/ordered-capabilities-epic.json
View on GitHub{
"_note": "Fixture for eval 3 — Epic whose Success Metrics are listed in logical dependency order (view before filter, filter before export). Tests that the proposed Feature list respects the natural capability ordering implied by the metrics.",
"epic": {
"number": 3,
"title": "Epic: Settlement Reporting Suite",
"labels": [{ "name": "epic" }],
"body": "## Goal\nA complete reporting suite so Merchants can find and export their settlement records, and Finance Managers can run cross-merchant analytics.\n\n## Context\nThe settlement reporting capability is currently absent. Merchants need sequential access: they must first see their settlements before they can filter them, and must filter before a meaningful export is possible. Finance Managers need aggregate visibility before they can identify anomalies. Building these capabilities in the wrong order would produce a feature set that is unusable until all parts are present.\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\n1. Merchant can see their settlement list\n2. Merchant can filter settlements by date and status\n3. Merchant can export filtered results as CSV\n4. Finance Manager can view all-merchant settlement summary\n5. Finance Manager can flag anomalous settlements\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 | 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 |