Plan work too big for one agent session as a shared map of decision tickets on GitHub Issues or Jira, then resolve them one at a time until the route is clear. Use with /wayfinder when the user says "plan something too big for one session", "chart a map", "wayfind", "work the map", or "decision tickets". Always confirm tracker (GitHub vs Jira) and destination before writing. Adapted from mattpocock/skills wayfinder (MIT).

2026-07-163

handoff

damian87x/oh-my-copilot

Create or resume a task handoff so a fresh agent can continue unfinished work. Persist via omp handoff CLI (never write handoff files yourself). Use when the user says /handoff, wants to pause mid-task, or resume prior work.

2026-07-153

ralph

damian87x/oh-my-copilot

Single-owner execute-fix-verify loop for one clear task. Use with /ralph when one agent should keep going until evidence or blocker.

2026-07-053

ultraqa

damian87x/oh-my-copilot

Adversarial QA pass that tests behavior, failures, and regressions. Use with /ultraqa after implementation when shallow checks are not enough.

2026-07-053

name	debug
description	Reproduce, minimize, diagnose, fix, and regression-test a bug. Use with /debug for broken, failing, slow, or confusing behavior.
argument-hint	<symptom or error message>

Debug

Use /debug for broken, failing, slow, or confusing behavior.

When to use

Tests are failing
Something is broken or throwing errors
Performance is unexpectedly slow
Behaviour is confusing or inconsistent

Steps (follow in order)

Reproduce — get the failure to happen reliably. If you can't reproduce, that's important information. For a web UI bug, use /qa-browse to drive the page and reproduce the broken flow.
Minimise — find the smallest case that still fails. Strip away unrelated code/config.
Hypothesise — form 2–3 ranked theories about the cause. Start with the most likely.
Inspect — gather evidence for/against each hypothesis. Read code, add logging, check state.
Fix — address the root cause, not just the symptom. If the fix is in the wrong layer, note it.
Regression test — add or run a test that would have caught this bug. Verify it passes now.

Rules

Never guess-and-check without a hypothesis
If the first fix doesn't work, don't keep patching — re-examine the hypothesis
Document what you tried and why it did/didn't work

Output

Repro — steps to reproduce the issue
Cause — root cause with file:line evidence
Fix — what was changed and why
Regression test — test that proves the fix and prevents recurrence