janmarkuslanger-engineering

Full architecture review of an implemented feature or module. Evaluates against clean design principles — single responsibility, dependency direction, layer separation, and interface quality — and produces actionable findings.

Assesses the true cost a change introduces — added complexity, new infrastructure (a database, a queue, a service), new dependencies, and ongoing operational and maintenance burden. Works on a pull request, a branch, or a described feature idea, and ends with a blunt bottom-line list of what the change costs. Asks which case to assess first.

Analyzes a module or codebase for coupling quality. Distinguishes intentional from accidental coupling, identifies problematic dependencies, and recommends concrete improvements.

Creates an Architecture Decision Record (ADR) for a significant design decision. Captures context, considered alternatives, the chosen option, and consequences — so future engineers understand why, not just what.

Saves the current agent state to HANDOFF.md so another agent can take over seamlessly. Captures completed work, open tasks, changed files, and next steps.