code-review

Turn an agreed plan, specification, or conversation into verifiable local tasks with acceptance criteria and explicit blocking dependencies.

Teach an engineering or research topic across sessions using a concrete learning goal, exercises, feedback, and evidence of understanding.

Synthesize an agreed conversation and repo context into a local specification with scope, public contracts, and acceptance evidence.

Implement agreed work from a specification or selected tickets, verify it through incremental checks, and finish with standards/spec review.

Build or sharpen project terminology, resolve ambiguous domain relationships, and maintain a glossary and consequential architecture decisions.

Survey a scoped existing codebase for architectural friction and rank behavior-preserving refactoring candidates before implementation.

Build a bounded throwaway prototype to answer a logic, state-model, or UI design question before implementing the maintained solution.

Interview a plan or design while recording resolved domain terms and consequential decisions in project documents.

Grill the user relentlessly about a plan, decision, or idea.

Test-driven development.

Diagnosis loop for hard bugs and performance regressions.

Shared vocabulary for designing deep modules.