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/questioning-style.md
View on GitHub# Questioning Style
How any wtf skill should use `AskUserQuestion` when gathering context from the user.
## Load the tool schema — do this now
`AskUserQuestion` is a deferred tool. Call this **immediately upon loading this reference**. Do it before any research or skill steps begin:
```
ToolSearch(query: "select:AskUserQuestion")
```
One call now keeps the schema loaded for the whole session.
## Core rules
1. **One question at a time.** Wait for the answer before asking the next. Do not batch questions into a single message. Batching makes the UI confusing. It also makes the answers hard to route.
2. **Always use `AskUserQuestion`**. Include open-ended questions like "What are the success criteria?" or "Who is the stakeholder?". Free-text-only prompts make research-backed suggestions invisible to the user. They also skip a chance to narrow the answer space.
3. **Pre-fill options from research.** For each question, infer 1–2 likely answers from the codebase, issue history, or prior conversation. Pass them as `options`. The user can still type a free-text answer. The UI appends an "Other (type your answer)" escape hatch. Do NOT add one manually.
4. **Prioritize by urgency.** Ask the questions that most constrain the draft first. Stop when you have enough to write a complete draft. Do not run through every possible question.
5. **Skip what research answered.** Topics already addressed by research, prior answers, or loaded context (Epic/Feature/steering docs) must be skipped silently. Re-asking them costs trust.
6. **Acknowledge briefly between answers.** One sentence max. Do not re-explain the prior answer. Move on.
## Compact notation in skill files
Skill files describe asks in a compact form. When you reach an `Ask` step, **stop and call `AskUserQuestion` immediately**. Do not output text. The compact notation maps directly to tool parameters:
Call `AskUserQuestion` with:
- **question** — the literal text in straight double quotes
- **header** — the value after `header` (in backticks in the notation)
- **options** — derived from the sub-list or inferred from research (see core rule 3)
Every `Ask` in a skill is a tool call — including the "Offer to continue" and "next step" routing questions at the end of a skill. Options printed as text bullets never reach the option picker, so do not substitute them for the call.
Wrong — outputs text bullets:
```
Next step
— Plan all Features → /wtf.epic-to-features for #427
— Write one Feature → start with one feature under #427
— Stop here
```
Right — calls the tool:
```
AskUserQuestion(
question: "What's next?",
header: "Next step",
options: [
{label: "Plan all Features", description: "Run /wtf.epic-to-features for #427"},
{label: "Write one Feature", description: "Start with one feature under #427"},
{label: "Stop here", description: "Exit, no further action"},
]
)
```
**Form 1 — inline** (inferred options, source-driven):
> Ask "Which Feature does this belong to?" — header `Feature`, options from recent open issues labeled `feature`.
**Form 2 — sub-list** (explicit options or branching):
> Ask "Does this look right?" — header `Review`:
> - **Looks good** → proceed with creation
> - **I have changes** → revise first
**Form 3 — mixed** (inferred candidates plus a static fallback):
> Ask "Which Epic does this Feature belong to?" — header `Epic`:
> - Candidates from recent open issues labeled `epic`
> - **None** — no parent Epic exists yet
### Operators
- `→` — branch action ("what the skill does next on this answer"). Use for routing decisions.
- `—` — description ("what this option means"). Use when the option needs clarification but does not branch the flow.
### Conventions
- Wrap the question in straight double quotes. It is the literal user-facing text.
- Wrap the header in backticks. It is the UI tag the user sees.
- Drop the "1–2 likely options" boilerplate. Rule 3 enforces it.
- For conditional asks ("if X is present, ask…"), put the condition before the `Ask` clause.
## When to ask in a single message instead
Rare. Only when three conditions all hold. The questions are tightly coupled. The answers are short. No answer changes which other questions are needed. Even then, prefer `AskUserQuestion` with options when at least one question has a constrained answer space.
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 |