Wat

You don't remember every skill, so ask.

Start at the lightest step that fits. A small, settled request can go directly to /tracer-implement; use an interview or spec only when it resolves uncertainty or creates useful durable context. A huge, foggy effort enters through Wayfinder. Entry-point workflows are user-invoked rather than auto-triggered.

The main flow: idea → ship

1. /tracer-interview-me — start here. A relentless interview worked as a design tree: each round asks the entire frontier of currently answerable questions at once, numbered, each with a recommended answer. Facts get looked up by sub-agents; decisions are yours. In a codebase it's docs-aware — existing CONTEXT.md/ADRs prune the tree before round 1, and settled terms/decisions get written back; with no codebase it runs stateless. If a frontier question needs a runnable answer (does this state model feel right, what should this UI look like), detour through /tracer-prototype — throwaway code that answers the question; keep the answer, delete the code. Done when the frontier is empty and nothing is silently assumed — then it hands off to /tracer-to-spec.

2. /tracer-to-spec: synthesize settled decisions into concise acceptance criteria, safety limits, and focused verification. Preserve explicit decisions without turning implementation suggestions into requirements. Skip the spec for a small request that is already clear.

3. Branch — is this a multi-session build?

   • Yes → /tracer-to-tickets: split the spec into tracer-bullet vertical slices, each declaring its blocking edges. Then kick off /tracer-implement per ticket, clearing context between each one.
   • No → /tracer-implement right here.

4. Choose how much control to keep:

   • /tracer-implement: approve a short approach and focused checks, implement in one context, then review once. Repair accepted defects in one pass and recheck corrections only if code changed. Report evidence and concerns, leaving the branch in place.
   • /tracer-autopilot: the same proportionate delivery without routine approval checkpoints, followed by your explicit branch-finishing choice. Custom infrastructure or stronger guarantees still require a decision. Review/repair limits survive resumes; unresolved material work is Blocked.