dotfiles

Product interrogation before commitment. Challenges whether you're solving the right problem for the right user at the right time. Use when starting a feature, exploring an idea, or before writing a spec. Triggers: "should I build this", "office hours", "is this worth building", "product check", "challenge this idea".

Find-fix-verify-regress loop for web apps using Chrome MCP. Use when asked to "qa this", "test the app", "find bugs", "does this work in the browser", "check the UI", "smoke test". Navigates the app, finds bugs, fixes code, verifies fixes, writes regression tests.

Trace how a change in one orchestration stack project (Ralph, Flow, Bach) affects the others. Invoke when editing contract-adjacent code — signal handling, state.json writes, task envelopes, worker dispatch, or iteration logic.

Apply Strunk's writing rules to prose—documentation, commits, error messages, UI text. Clearer, stronger, more professional.

This skill should be used when the user asks to "research X", "investigate Y", "look into Z", "find out about", "what are the options for", "compare X vs Y", "how does X work", or requests technical investigation of libraries, APIs, frameworks, or architectural approaches.

Framework for code review that captures context future maintainers need—concerns raised, alternatives rejected, risks accepted. Use for PRs, local changes, or architecture review when the decision matters more than the diff. Produces structured feedback with must-address issues, suggestions, and observations "for the record."