Skip to content

xiduzo/wtf / skills/wtf.setup

wtf.setup

Verified

This 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.

references/FEATURE.md

View on GitHub
---
name: Feature
about: A user-facing capability within an Epic
title: "πŸš€ Feature: "
labels: feature
assignees: ""
---

# πŸš€ Feature: {{title}}

## Bounded Context

---

## User Stories

<!-- πŸ‘€ PO β€” 1..n co-related stories that share one Spine. This body is canonical for all scenarios: PMs and designers edit them here, not in Trace issues. Repeat the story block for each story. -->

### Story 1: [name]

- As a **_, I want _** so that \_\_\_

#### Acceptance Criteria

<!-- Each AC maps to one or more scenarios below. -->

- [ ]

#### Scenarios

<!-- Canonical Gherkin for this story. Traces claim subsets of these by name. -->

```gherkin
Scenario: Happy path
  Given
  When
  Then

Scenario: Edge case
  Given
  When
  Then
```

## Design Handoff

<!-- Link Figma frames, component specs, or annotated mockups -->

- Figma:
- States covered: (default / loading / error / empty)
- Accessibility notes:

---

## Edge Cases

<!-- Explicitly name them here so Deepening Traces can claim scenarios that cover them. Use domain language. -->

-

---

## Domain Events

<!-- Events this feature emits or consumes. Use past-tense domain names (e.g. OrderPlaced, PaymentSettled). -->

- Emits:
- Consumes:

---

## Definition of Ready

<!-- This feature is ready for a Trace Plan when: -->

- [ ] User stories agreed by PO
- [ ] Design handoff complete
- [ ] Acceptance criteria written and reviewed
- [ ] Edge cases identified

---

## Trace Plan

<!-- Ordered checklist β€” the current aim, not a contract. Item 1 is the Skeleton. Every further story gets one Extension before its Deepenings. Each item names its Spine Position, its story, its Scenario Claim, and what it adds to the Spine. Link Trace issues as they are created. -->

1. [ ] β˜„οΈ Skeleton β€” [primary story]: [what it proves of the Spine] (claims: "[scenario name]")
2. [ ] β˜„οΈ Extension β€” [further story]: [what it adds to the Spine] (claims: "[scenario name]")
3. [ ] β˜„οΈ Deepening β€” [story already started]: [what it adds to the Spine] (claims: "[scenario names]")

---

## Delivery Override

<!-- Optional. Set only when this Feature must not use the `delivery` mode in `.wtf/config.json`. State the reason. Leave blank to use the config. -->

- Mode: <!-- staged | trunk -->
- Reason:
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