Skip to content

xiduzo/wtf / skills/wtf.refine

wtf.refine

Verified

Use when new insights change the scope, acceptance criteria, scenarios, domain language, or technical constraints of an existing Epic, Feature, or Trace — for example "refine epic

evals/fixtures/domain-language-correction.json

View on GitHub
{
  "_note": "Legacy Task issue (label `task`, pre-Trace-model shape with in-body Gherkin) using 'Customer' throughout. Kept deliberately as a legacy Task: the skill must detect it and treat it as a legacy Trace whose in-body Gherkin is canonical and edited in place (the scenario canonicality guard does not fire). Insight: domain language correction — use 'Merchant' instead. Expected change map: legacy Trace detected, DDD language changed yes, Gherkin steps affected yes, Contracts affected yes.",
  "issue": {
    "number": 31,
    "title": "Task: Send settlement confirmation to customer",
    "labels": [{"name": "task"}],
    "body": "## Intent\nNotify the customer by email when their settlement has been processed and funds are on their way.\n\n## Functional Description\nAfter a settlement is marked as `processed`, the system sends a confirmation email to the customer's registered email address. The email includes the settlement amount, reference number, and expected arrival date.\n\n## Gherkin\n```gherkin\nFeature: Settlement confirmation email\n\n  Scenario: Customer receives confirmation after settlement is processed\n    Given a customer has a settlement in status \"pending\"\n    When the settlement status changes to \"processed\"\n    Then the customer receives a confirmation email\n    And the email contains the settlement amount\n    And the email contains the reference number\n\n  Scenario: Customer with unverified email does not receive confirmation\n    Given a customer has an unverified email address\n    When their settlement is processed\n    Then no confirmation email is sent\n    And a warning is logged for manual follow-up\n```\n\n## Contracts\n- Input: `SettlementProcessed` domain event — fields: `customerId`, `settlementId`, `amount`, `currency`, `expectedArrival`\n- Output: Email queued in `notifications` service — `to: customer.email`, `templateId: settlement-confirmation`\n- Precondition: Customer's email must be verified\n- Postcondition: `NotificationQueued` event emitted with `customerId` and `notificationId`\n\n## Technical Approach\nListen to `SettlementProcessed` via the event bus. Look up customer record by `customerId`. Check `email_verified` flag. Queue notification via `NotificationService.queue()`.\n\n## Observability\n- Log: `settlement.confirmation.queued` with `customerId`, `settlementId`\n- Log: `settlement.confirmation.skipped` with `customerId`, `reason: email_not_verified`"
  }
}
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall