@muthukumaran-k-1

ucts-investigate guides systematic root-cause debugging through hypothesis formation, data tracing, and minimal testing. enforces investigation before fixes and stops after three failed attempts to force reassessment.

ucts-office-hours guides product strategy through six forcing questions that demand specificity over abstraction, then synthesizes findings into tiered implementation approaches with a single success metric.

ucts-retro guides teams through structured weekly retrospectives covering shipped work, incidents, friction points, and concrete action items. designed for synchronous facilitation without requiring a separate code session.

ucts-guide classifies coding tasks across complexity, domain, scope and risk dimensions, then prescribes tool combinations and dispatch instructions for optimized claude code sessions.