Results for “research-before-coding”

Turns a spec or requirements into a detailed, bite-sized implementation plan with exact file paths, code, and test steps for engineers with no codebase context.

Enforces evidence-based completion claims and rigorous code review practices, including receiving feedback, requesting reviews, and verification gates.

Enforces code review practices: receiving feedback with technical rigor, requesting reviews via /code-review, and verifying before claiming completion.

Guide for refactoring code to improve quality without changing behavior. Use when refactoring, cleaning up code, reducing duplication, improving readability, or restructuring code. Integrates Firecrawl for researching modern patterns before refactoring, and codebase-aware dependency analysis to avoid breaking changes.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.