BaxterCooper
@BaxterCooper
Public Skills
context-gathering
by BaxterCooper
Use when entering an unfamiliar codebase, starting a new feature, or before any implementation task. Provides structured exploration protocol to understand before acting.
error-recovery
by BaxterCooper
Use when tasks fail due to transient errors. Provides structured retry strategies and graceful degradation patterns. Invoke on network errors, rate limits, or intermittent failures.
estimation
by BaxterCooper
Use before committing to a task. Provides complexity analysis and scope assessment. Invoke when user asks "how complex" or before large features.
systematic-debugging
by BaxterCooper
Invoke when debugging failures. MANDATORY when 3+ fix attempts have failed. Enforces root cause investigation before fixes.
finishing
by BaxterCooper
Use when all tasks are complete. Presents completion options and enforces test gate. Work is never left in limbo.
orchestration
by BaxterCooper
This skill should be used when orchestrating complex tasks, decomposing work into atomic units, dispatching to subagents, verifying outputs, or when discussing task verification and deviation tracking patterns.
tdd
by BaxterCooper
Use for any code implementation task. Enforces RED-GREEN-REFACTOR cycle. "If you didn't watch it fail, you don't know if it tests the right thing."
verification
by BaxterCooper
This skill MUST be invoked before any completion claim, success report, or task transition. Mandates 5-step evidence protocol. Use when about to claim "done", "complete", "working", "fixed", or any success state.
writing-plans
by BaxterCooper
Use when creating implementation plans. Mandates exact file paths, complete code samples, and expected output. No vague language allowed.
parallel-dispatch
by BaxterCooper
Use when facing multiple tasks or failures. Provides decision framework for concurrent vs sequential execution. Invoke before dispatching multiple subagents.