Skip to content

xiduzo/wtf / skills/wtf.feature-to-traces

wtf.feature-to-traces

Verified

This 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

evals/fixtures/complex-edge-case.json

View on GitHub
{
  "_note": "Fixture for eval 3 — legacy-shape Feature (no Trace Plan) with two stories, where one AC (chunked ZIP export for large datasets) is far more complex than the rest. Expected: a derived Trace Plan with exactly one Skeleton first claiming the primary story's happy path (basic CSV download), the chunked ZIP export as its own Deepening entry citing its story, and the filtered-export story delivered by its own entry. Split by depth — never a separate backend/frontend or migration entry.",
  "feature": {
    "number": 50,
    "title": "Feature: Settlement CSV export",
    "labels": [{ "name": "feature" }, { "name": "designed" }],
    "body": "## Goal\nAllow merchants to download their settlement data as a CSV file so they can perform offline analysis and import into accounting tools.\n\n## Bounded Context\nSettlement\n\n## User Stories\n- As a Merchant, I want to download my settlements as a CSV file so that I can analyse them in a spreadsheet.\n- As a Merchant, I want any active filters to be applied to my CSV export so that I only export the data I can see on screen.\n\n## Acceptance Criteria\n- AC1: A merchant can trigger a CSV download from the settlement list UI; the file contains all columns visible in the list.\n- AC2: When filters (e.g. date range, status) are active, the exported CSV reflects those filters — only matching settlements are included.\n- AC3: Exports containing more than 10,000 rows are chunked into multiple CSV files and delivered to the merchant as a single ZIP archive; a progress indicator is shown while the archive is being prepared.\n\n## Edge Cases\n- Exporting zero results produces an empty CSV with the header row only.\n- Chunking boundary falls exactly on 10,000 rows: the archive contains two files, each up to 10,000 rows.\n- If the ZIP preparation exceeds 60 seconds, the merchant receives an email link to download the archive instead.\n\n## Domain Events\n- `SettlementExportRequested` — emitted when a merchant initiates an export.\n- `SettlementExportReady` — emitted when the export file or archive is ready for download."
  }
}
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall