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/migration-implied.json

View on GitHub
{
  "_note": "Fixture for eval 1 — legacy-shape Feature (no Trace Plan, no canonical scenarios) whose ACs imply a database schema migration. The old task model made the migration a separate first task. The Trace model must NOT: the schema change rides inside the Skeleton, which claims the story's happy path end-to-end through every layer. Expected: a derived Trace Plan with exactly one Skeleton first and Deepening entries for the edge cases — no standalone migration entry, no layer entries.",
  "feature": {
    "number": 42,
    "title": "Feature: Track settlement processing fees",
    "labels": [{ "name": "feature" }, { "name": "designed" }],
    "body": "## Goal\nAllow the system to record and expose the processing fee charged for each settlement so that merchants can reconcile costs accurately.\n\n## Bounded Context\nSettlement\n\n## User Stories\n- As a Merchant, I want to see the processing fee for each settlement so that I can match it against my payment provider invoice.\n\n## Acceptance Criteria\n- AC1: The settlement record includes a processing fee amount stored persistently (requires a new `fee` column on the settlements table).\n- AC2: The fee is calculated automatically from the settlement total using the configured fee rate when a settlement is processed.\n- AC3: The `GET /settlements/:id` API response includes a `processingFee` field.\n- AC4: The settlement list UI displays the processing fee alongside the settlement total.\n\n## Edge Cases\n- Fee is zero when the settlement total is zero.\n- Fee calculation rounds to two decimal places using standard banker's rounding.\n\n## Domain Events\n- `SettlementFeeCalculated` — emitted after fee is applied to a settlement record."
  }
}
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