xiduzo/wtf / skills/wtf.write-trace
wtf.write-trace
VerifiedThis skill should be used when a user wants to create a single Trace issue under a Feature — for example "create a trace", "write a trace for this feature", "add a trace to feature
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.3 KB |
| evals/evals.json | config | 4.8 KB |
| evals/fixtures/ambiguous-claim.json | config | 2.7 KB |
| evals/fixtures/claim-selection.json | config | 2.9 KB |
| evals/fixtures/depth-split-draft.json | config | 3.4 KB |
evals/fixtures/claim-selection.json
View on GitHub{
"_note": "Feature in the Trace-model shape: one story with four canonical Gherkin scenarios, a Trace Plan whose Skeleton entry is created (#56), and one existing child Trace claiming the happy path. Eval: produce the Story and Scenario Claim sections for plan entry 2. Scenarios must be copied verbatim from the Feature — never re-derived — and must not overlap the Skeleton's claim.",
"feature": {
"number": 55,
"title": "🚀 Feature: Settlement PDF export",
"labels": [{ "name": "feature" }],
"body": "## Bounded Context\nSettlement domain. Merchant actor. Reads from settlement records; no write side effects.\n\n## User Stories\n\n### Story 1: Export settlement history as a PDF\n\n- As a **Merchant**, I want **to export my settlement history as a PDF** so that **I can satisfy my accounting and audit needs**\n\n#### Acceptance Criteria\n\n- [ ] Merchants can trigger a PDF download of their settlement history\n- [ ] The PDF includes a header with the Merchant name, export date, and date range\n- [ ] An empty result set produces a PDF with headers and a 'No settlements found' message\n- [ ] Only Merchants with the settlement.export permission can trigger an export\n\n#### Scenarios\n\n```gherkin\nScenario: Merchant downloads a settlement PDF\n Given a Merchant with the settlement.export permission has settlements in the selected date range\n When the Merchant triggers a PDF export\n Then the Merchant receives a PDF of the settlement history for that range\n\nScenario: PDF header shows Merchant name and date range\n Given a Merchant has triggered a PDF export\n When the export completes\n Then the PDF header shows the Merchant name, the export date, and the selected date range\n\nScenario: Empty settlement range produces a placeholder PDF\n Given a Merchant has no settlements in the selected date range\n When the Merchant triggers a PDF export\n Then the PDF shows 'No settlements found' with the headers intact\n\nScenario: Merchant without export permission sees no export action\n Given a Merchant without the settlement.export permission\n When the Merchant views the settlement history\n Then no export action is available\n```\n\n## Domain Events\n\n- Emits: `SettlementExportRequested`, `SettlementExportReady`\n- Consumes: none\n\n## Trace Plan\n\n1. [x] ☄️ Skeleton — Export settlement history as a PDF: proves the export path end-to-end (claims: \"Merchant downloads a settlement PDF\") #56\n2. [ ] ☄️ Deepening — Export settlement history as a PDF: header, empty range, and permission gate (claims: \"PDF header shows Merchant name and date range\", \"Empty settlement range produces a placeholder PDF\", \"Merchant without export permission sees no export action\")"
},
"traces": [
{
"number": 56,
"title": "☄️ Trace: Skeleton — settlement PDF export",
"labels": [{ "name": "trace" }, { "name": "implemented" }],
"scenario_claim": ["Merchant downloads a settlement PDF"]
}
]
}
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 |