0xrizz

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Testing & QA Listed

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

clean-system

Use when ext4 disk space is low, package caches are bloated, or after intensive development builds requiring APT, UV, PNPM, Bun, and /tmp cache eviction

Data & Documents Listed

dotfiles

Use when backing up, comparing, or restoring user shell configuration dotfiles (~/.bashrc, ~/.tmux.conf, ~/.gitconfig) against versioned backups

harness-check

Use when verifying Claude Code harness integrity, running the security hook test suite, validating multi-agent skill symlinks, or checking settings.json syntax

perf-tune

Use when measuring I/O latency between ext4 and 9P Windows mounts, running disk throughput benchmarks, or diagnosing filesystem performance bottlenecks

sys-diag

Use when diagnosing system health issues, checking RAM/swap pressure, inspecting storage utilization, verifying systemd service failures, or analyzing WSL2 kernel metrics

tmux-agents

Use when launching a multi-agent terminal workspace, pairing Claude Code with Google Antigravity (agy), or reattaching to an active multi-pane agent session

update-runtimes

Use when upgrading system packages, refreshing development runtimes (Node, PNPM, Bun, UV), or updating AI coding CLIs to their latest stable releases

wsl-snapshot

Use when creating point-in-time backups of the Debian WSL2 environment, exporting disk snapshots to external Windows storage, or verifying backup archive integrity