drvoss

Use when a plan still has hidden assumptions — default to one question at a time for dependent branches, batch only truly independent…

Use when a plan must be stress-tested against the codebase's existing language and decisions — grill it against current docs, glossary…

Use when work is changing sessions, agents, or machines and the next pass needs a compact handoff document with current state, open…

Use when starting implementation work from a PRD, spec, or set of issues — to follow a structured TDD → validate → review → commit loop.

Use after an implementation pass lands — compare the original task spec or handoff against the delivered diff, classify each requested…

Use when a codebase feels hard to change, test, or navigate — surface architectural friction, identify deeper module seams, and walk one…

Use when a request is underspecified and you need to discover what the user actually wants before writing a plan, spec, or code - default…

Use when you're preparing to launch a product or feature publicly — builds a structured checklist covering positioning, distribution…

Use when research or domain knowledge keeps getting rediscovered across sessions — build a supplementary markdown wiki that compounds…

Use when you need to build a new MCP server — plan the tool surface, implement the server, register it in Copilot CLI, inspect the config…

Use when performance is a real concern — measure first, isolate the bottleneck, and prove the improvement instead of guessing

Use when engineering needs testable, implementable technical requirements — not a PRD but a capability spec with acceptance criteria, task…