xiduzo/wtf / skills/wtf.setup
wtf.setup
VerifiedThis skill should be used when a user wants to set up WTF in a repository or check that the environment is ready for it — for example "set up wtf", "is wtf ready", "install wtf templates", or "a new dev joined, set them up". Verifies the GitHub CLI and its auth, installs the required gh extensions and the issue and PR templates, configures issue classification, planning, feature scope, and delivery mode, and registers the hooks. Run once per repo when onboarding, or when a contributor joins the project.
shared-references/ddd-writing-rules.md
View on GitHub---
name: DDD Writing Rules
description: Shared DDD vocabulary and anti-pattern rules for writing Epics, Features, and Traces in Ubiquitous Language. Referenced by write-epic, write-feature, and write-trace.
---
# DDD Writing Rules
Apply these rules whenever you write or review Epic, Feature, or Trace content.
## Prose mechanics (STE)
Sentence shape, tense, voice, and non-domain vocabulary follow strict STE in `ste-writing.md`.
DDD chooses *which* domain term (actor, verb, object, event). Those terms feed the STE DDD allowlist as technical nouns and technical verbs.
Apply both references before you write durable bodies.
## Domain Actor Naming
Use named domain roles. Never use generic terms:
- ✅ "Fulfilment Manager", "Payment Auditor", "Merchant"
- ❌ "user", "admin", "the system"
## Domain Verb vs CRUD
Use business actions. Do not use generic CRUD verbs:
- ✅ allocate, settle, reconcile, dispute, approve, fulfil, cancel
- ❌ create, update, delete, store, query, render, process
## Domain Event Naming
Events must use **past-tense domain names** from the **domain's perspective**:
- ✅ `OrderPlaced`, `PaymentSettled`, `ShipmentDispatched`
- ❌ `order_status_updated`, `payment_processed_successfully`, `ShipmentServiceUpdatedStatus`
## Business Outcomes, Not System States
Describe observable business results. Do not describe technical system state:
- ✅ "The Merchant receives a settlement notification within 2 minutes"
- ❌ "The `orders` table has `status = 'settled'`", "HTTP 200 returned"
## Tech Jargon Anti-Patterns
Remove these from any domain-facing content (Epic goals, Feature ACs, Gherkin scenarios, user stories):
- REST API, HTTP, JSON payload, SQL query, database record/row/table
- Mock, stub, endpoint, microservice, lambda
- Any implementation framework name in a business description
Reframe in business terms before you write.
## Bounded Context Seams
Name every bounded context explicitly. When a Feature or Trace crosses a seam:
- Identify which context **emits** and which **consumes**
- Use each context's own vocabulary on its side of the seam
- Example: "Sales Context emits `OrderPlaced`. Warehouse Context consumes it."
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: 471k | 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 |