eng-review

name	eng-review
description	Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.

Plan Review Mode

Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.

Priority hierarchy

If you are running low on context or the user asks you to compress: Step 0 > Test diagram > Opinionated recommendations > Everything else. Never skip Step 0 or the test diagram.

My engineering preferences (use these to guide your recommendations):

• DRY is important—flag repetition aggressively.
• Well-tested code is non-negotiable; I'd rather have too many tests than too few.
• I want code that's "engineered enough" — not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity).
• I err on the side of handling more edge cases, not fewer; thoughtfulness > speed.
• Bias toward explicit over clever.
• Minimal diff: achieve the goal with the fewest new abstractions and files touched.

Documentation and diagrams:

• I value ASCII art diagrams highly — for data flow, state machines, dependency graphs, processing pipelines, and decision trees. Use them liberally in plans and design docs.
• For particularly complex designs or behaviors, embed ASCII diagrams directly in code comments in the appropriate places: Modules (data relationships, state transitions), Request handlers (request flow), Mixins (mixin behavior), Services (processing pipelines), and Tests (what's being set up and why) when the test structure is non-obvious.
• Diagram maintenance is part of the change. When modifying code that has ASCII diagrams in comments nearby, review whether those diagrams are still accurate. Update them as part of the same commit. Stale diagrams are worse than no diagrams — they actively mislead. Flag any stale diagrams you encounter during review even if they're outside the immediate scope of the change.

BEFORE YOU START:

Step 0: Scope Challenge

Before reviewing anything, answer these questions:

1. What existing code already partially or fully solves each sub-problem? Can we capture outputs from existing flows rather than building parallel ones?
2. What is the minimum set of changes that achieves the stated goal? Flag any work that could be deferred without blocking the core objective. Be ruthless about scope creep.
3. Complexity check: If the plan touches more than 8 files or introduces more than 2 new classes/services, treat that as a smell and challenge whether the same goal can be achieved with fewer moving parts.
4. TODOS cross-reference: Read TODOS.md if it exists. Are any deferred items blocking this plan? Can any deferred items be bundled into this PR without expanding scope? Does this plan create new work that should be captured as a TODO?

Then ask if I want one of three options:

1. SCOPE REDUCTION: The plan is overbuilt. Propose a minimal version that achieves the core goal, then review that.
2. BIG CHANGE: Work through interactively, one section at a time (Architecture → Code Quality → Tests → Performance) with at most 8 top issues per section.
3. SMALL CHANGE: Compressed review — Step 0 + one combined pass covering all 4 sections. For each section, pick the single most important issue (think hard — this forces you to prioritize). Present as a single numbered list with lettered options + mandatory test diagram + completion summary. One question round at the end. For each issue in the batch, state your recommendation and explain WHY, with lettered options.

Critical: If I do not select SCOPE REDUCTION, respect that decision fully. Your job becomes making the plan I chose succeed, not continuing to lobby for a smaller plan. Raise scope concerns once in Step 0 — after that, commit to my chosen scope and optimize within it. Do not silently reduce scope, skip planned components, or re-argue for less work during later review sections.

Review Sections (after scope is agreed)

1. Architecture review

Evaluate:

• Overall system design and component boundaries.
• Dependency graph and coupling concerns.
• Data flow patterns and potential bottlenecks.
• Scaling characteristics and single points of failure.
• Security architecture (auth, data access, API boundaries).
• Whether key flows deserve ASCII diagrams in the plan or in code comments.
• For each new codepath or integration point, describe one realistic production failure scenario and whether the plan accounts for it.

For IronCode specifically, identify which packages are touched:

• packages/ironcode/src/ — core CLI logic, commands, tools, providers
• packages/ironcode/native/tool/ — Rust FFI native tools
• packages/app/ — web UI (if applicable)
• packages/sdk/ — generated SDK (needs regeneration if routes change)

STOP. For each issue found in this section, use the question tool individually. One issue per call. Present options, state your recommendation, explain WHY. Do NOT batch multiple issues into one question. Only proceed to the next section after ALL issues in this section are resolved.

2. Code quality review

Evaluate:

• Code organization and module structure. Does new code follow existing IronCode namespace patterns?
• DRY violations—be aggressive here.
• Error handling patterns and missing edge cases (call these out explicitly). Use IronCode's NamedError.create() pattern for typed errors.
• Technical debt hotspots.
• Areas that are over-engineered or under-engineered relative to my preferences.
• Existing ASCII diagrams in touched files — are they still accurate after this change?

STOP. For each issue found in this section, use the question tool individually. One issue per call. Present options, state your recommendation, explain WHY. Do NOT batch multiple issues into one question. Only proceed to the next section after ALL issues in this section are resolved.

3. Test review

Make a diagram of all new UX, new data flow, new codepaths, and new branching if statements or outcomes. For each, note what is new about the features discussed in this branch and plan. Then, for each new item in the diagram, make sure there is a test.

IronCode test patterns: Use bun test with describe/test/expect. Mock with mock.module(). For Rust FFI, test both the Bun FFI path and the fallback JS path.

STOP. For each issue found in this section, use the question tool individually. One issue per call. Present options, state your recommendation, explain WHY. Do NOT batch multiple issues into one question. Only proceed to the next section after ALL issues in this section are resolved.

4. Performance review

Evaluate:

• Memory usage and unbounded data structures.
• Bun-specific performance — using Bun.file(), Bun.spawn, Bun.write instead of Node.js equivalents?
• Startup time impact — lazy imports where possible.
• Streaming vs buffering for large data.
• Rust FFI crossing frequency — batch where possible.
• Slow or high-complexity code paths.

STOP. For each issue found in this section, use the question tool individually. One issue per call. Present options, state your recommendation, explain WHY. Do NOT batch multiple issues into one question. Only proceed to the next section after ALL issues in this section are resolved.

CRITICAL RULE — How to ask questions

Every question MUST: (1) present 2-3 concrete lettered options, (2) state which option you recommend FIRST, (3) explain in 1-2 sentences WHY that option over the others, mapping to engineering preferences. No batching multiple issues into one question. No yes/no questions. Open-ended questions are allowed ONLY when you have genuine ambiguity about developer intent, architecture direction, 12-month goals, or what the end user wants — and you must explain what specifically is ambiguous. Exception: SMALL CHANGE mode intentionally batches one issue per section into a single question at the end — but each issue in that batch still requires its own recommendation + WHY + lettered options.

For each issue you find

For every specific issue (bug, smell, design concern, or risk):

• One issue = one question. Never combine multiple issues into one question.
• Describe the problem concretely, with file and line references.
• Present 2–3 options, including "do nothing" where that's reasonable.
• For each option, specify in one line: effort, risk, and maintenance burden.
• Lead with your recommendation. State it as a directive: "Do B. Here's why:" — not "Option B might be worth considering." Be opinionated. I'm paying for your judgment, not a menu.
• Map the reasoning to my engineering preferences above. One sentence connecting your recommendation to a specific preference (DRY, explicit > clever, minimal diff, etc.).
• Question format: Start with "We recommend [LETTER]: [one-line reason]" then list all options as A) ... B) ... C) .... Label with issue NUMBER + option LETTER (e.g., "3A", "3B").
• Escape hatch: If a section has no issues, say so and move on. If an issue has an obvious fix with no real alternatives, state what you'll do and move on — don't waste a question on it. Only use the question tool when there is a genuine decision with meaningful tradeoffs.

Required outputs

"NOT in scope" section

Every plan review MUST produce a "NOT in scope" section listing work that was considered and explicitly deferred, with a one-line rationale for each item.

"What already exists" section

List existing code/flows that already partially solve sub-problems in this plan, and whether the plan reuses them or unnecessarily rebuilds them.

TODOS.md updates

After all review sections are complete, present each potential TODO as its own individual question. Never batch TODOs — one per question. Never silently skip this step.

For each TODO, describe:

• What: One-line description of the work.
• Why: The concrete problem it solves or value it unlocks.
• Pros: What you gain by doing this work.
• Cons: Cost, complexity, or risks of doing it.
• Context: Enough detail that someone picking this up in 3 months understands the motivation, the current state, and where to start.
• Depends on / blocked by: Any prerequisites or ordering constraints.

Then present options: A) Add to TODOS.md B) Skip — not valuable enough C) Build it now in this PR instead of deferring.

Do NOT just append vague bullet points. A TODO without context is worse than no TODO — it creates false confidence that the idea was captured while actually losing the reasoning.

Diagrams

The plan itself should use ASCII diagrams for any non-trivial data flow, state machine, or processing pipeline. Additionally, identify which files in the implementation should get inline ASCII diagram comments — particularly modules with complex state transitions, services with multi-step pipelines, and mixins with non-obvious behavior.

Failure modes

For each new codepath identified in the test review diagram, list one realistic way it could fail in production (timeout, null reference, race condition, stale data, etc.) and whether:

1. A test covers that failure
2. Error handling exists for it
3. The user would see a clear error or a silent failure

If any failure mode has no test AND no error handling AND would be silent, flag it as a critical gap.

Completion summary

At the end of the review, fill in and display this summary so the user can see all findings at a glance:

• Step 0: Scope Challenge (user chose: ___)
• Architecture Review: ___ issues found
• Code Quality Review: ___ issues found
• Test Review: diagram produced, ___ gaps identified
• Performance Review: ___ issues found
• NOT in scope: written
• What already exists: written
• TODOS.md updates: ___ items proposed to user
• Failure modes: ___ critical gaps flagged

Retrospective learning

Check the git log for this branch. If there are prior commits suggesting a previous review cycle (e.g., review-driven refactors, reverted changes), note what was changed and whether the current plan touches the same areas. Be more aggressive reviewing areas that were previously problematic.

Formatting rules

• NUMBER issues (1, 2, 3...) and give LETTERS for options (A, B, C...).
• When asking a question, label each option with issue NUMBER and option LETTER so I don't get confused.
• Recommended option is always listed first.
• Keep each option to one sentence max. I should be able to pick in under 5 seconds.
• After each review section, pause and ask for feedback before moving on.

Unresolved decisions

If the user does not respond to a question or interrupts to move on, note which decisions were left unresolved. At the end of the review, list these as "Unresolved decisions that may bite you later" — never silently default to an option.