xiduzo/wtf / skills/wtf.feature-to-traces
wtf.feature-to-traces
VerifiedThis skill should be used when a user wants to plan and create the complete set of Traces for a Feature — for example "plan all traces", "create the traces for feature
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.3 KB |
| evals/evals.json | config | 4.8 KB |
| evals/fixtures/complex-edge-case.json | config | 2.1 KB |
| evals/fixtures/cross-layer-feature.json | config | 2.2 KB |
| evals/fixtures/migration-implied.json | config | 1.7 KB |
evals/fixtures/cross-layer-feature.json
View on GitHub{
"_note": "Fixture for eval 2 — legacy-shape Feature carrying a Proposed Tasks checklist sliced by LAYER (API filter, query optimisation, picker UI, URL persistence). The Trace model must refuse this slicing: a legacy Proposed Tasks list is not a Trace Plan. Expected: a derived spine-first plan — one Skeleton claiming the story's happy path through API and UI in one Trace, then Deepening entries for the edge cases — with the layer checklist explicitly not adopted.",
"feature": {
"number": 45,
"title": "Feature: Settlement date range filter",
"labels": [{ "name": "feature" }, { "name": "designed" }],
"body": "## Goal\nLet merchants filter their settlement list by a date range so they can focus on a specific billing period without scrolling through all records.\n\n## Bounded Context\nSettlement\n\n## User Stories\n- As a Merchant, I want to filter settlements by a start and end date so that I can view only the records relevant to a billing period.\n\n## Acceptance Criteria\n- AC1: The `GET /settlements` endpoint accepts optional `from` and `to` query parameters (ISO 8601 dates) and returns only settlements whose `settledAt` date falls within the range.\n- AC2: Settlement queries filtered by date range use an index on `settledAt` so that response times remain under 200 ms for datasets up to 500,000 rows.\n- AC3: The settlement list UI shows a date range picker that lets the merchant select a start and end date; applying the filter reloads the list with the chosen range.\n- AC4: The selected date range is persisted in the URL as `?from=YYYY-MM-DD&to=YYYY-MM-DD` so that filtered views are bookmarkable and shareable.\n\n## Edge Cases\n- When only `from` is provided the filter returns all settlements on or after that date.\n- When only `to` is provided the filter returns all settlements on or before that date.\n- Invalid date formats are rejected with a 400 response.\n\n## Domain Events\n- None — this feature is read-only.\n\n## Proposed Tasks\n- [ ] Add date range filter to settlements API\n- [ ] Optimise settlement query for date range lookups\n- [ ] Add date range picker component to settlement list UI\n- [ ] Wire URL query parameter persistence"
}
}
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 |