nix-config-v2

Use when starting a new feature, design change, or architecture decision. Explores approaches and tradeoffs before planning or coding. NEVER skip this for non-trivial work.

Use when executing an implementation plan. Each step is delegated to a fresh subagent for isolated context, then reviewed before proceeding. Do NOT execute plans inline — use subagents.

Use when implementation is complete and you need to decide how to integrate the work - guides completion by presenting structured options for merge, PR, or cleanup

Use when creating implementation plans. Breaks work into small, verifiable steps with exact file paths and verification commands. Use after brainstorming approval.

Use when you receive code review feedback (from a reviewer subagent, /review command, or human). Guides proper processing of feedback without dismissing or cherry-picking.

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

Use when implementing features or fixing bugs to determine whether tests should be written. Context-aware - scouts existing test infrastructure before deciding. Not all code needs tests.

Use before claiming any work is complete. Ensures actual verification evidence exists - tests run, builds pass, behavior confirmed. No hedging.

Use when creating new skills for the agent. Follows a test-driven approach - observe failure without the skill, write the skill, then verify it closes the gap.

Use when creating git commits, staging changes, or writing commit messages - defines commit format rules, conventional commits usage, ticket-branch handling, and AI attribution requirements

Use when considering parallel execution of multiple tasks. Guides when to parallelise vs sequence, how to partition work, and how to handle partial failures.

Use when starting new work, managing branches, or finishing features. Covers branch creation, commit discipline, and merge workflows.

Use when evaluating and addressing unresolved PR review comments, before implementing any fixes from code review feedback on a pull request

Use when creating git commits, staging changes, or writing commit messages - defines commit format rules, conventional commits usage, ticket-branch handling, and AI attribution requirements

Use when about to run any git worktree command (add, remove, list, prune), git clone for a new repo, or when the user asks to work on a different branch. Also use when you see git worktree in a plan or think about creating parallel working directories.