// Engineering go/no-go on a plan. Use after auto-plan, before execution.
| name | auto-eng-review |
| description | Engineering go/no-go on a plan. Use after auto-plan, before execution. |
| metadata | {"stage":"plan"} |
Engineering-safety gate. Validates that a plan is safe to execute before implementation begins.
First action: run scripts/get-context.mjs → JSON {activeChange, stage, canonicalSpec, canonicalDesign, canonicalPlan, productReview, engineeringReview, diagnostics} (missing state normalizes to "none"/null). If any diagnostic has level "error", stop and report it before proceeding. Read PLAN.md; read DESIGN.md only when canonical_design is set and resolves to a file.
Execution safety review. Architecture, data flow, edge cases, test strategy, not product vision. It does not modify the plan or reopen product scope. Identifies risks that could cause failure, stalling, or rework.
Loading discipline: one PLAN.md read, optional DESIGN.md when canonical_design exists, one risk matrix, one verdict. Read source files when assessing technical risk — slice boundaries, dependency assumptions, and blast radius claims are only verifiable against the actual code.
Before appending the engineering review:
references/quality.md (~36 lines: anti-patterns, better shape, prose hygiene scan patterns) when findings are generic or unactionable.Read .agent/steering/STATUS.md. Read the canonical PLAN.md. If canonical_design is null, missing, or points to a missing file, continue without DESIGN.md and note that the plan intentionally has no design artifact.
In engineering terms: what is being built, what systems does it touch, and what is the critical path?
Use this matrix as an internal checklist. In chat, summarize only the verdict-driving dimensions unless the user asks for the full matrix.
| Dimension | Rating (0–10) | What a 10 looks like |
|---|---|---|
| Architecture fit | Clean integration, no hacks, follows existing patterns | |
| Data flow clarity | Every input, transform, and output is traceable | |
| Edge case coverage | Failure modes are enumerated and handled | |
| Test strategy | Tests are specified before code, not after | |
| Rollback safety | Can revert without data loss or downtime | |
| Dependency risk | No new critical dependencies; existing ones are stable |
A score ≤ 3 in any dimension is a blocking concern. Surface it explicitly.
Use exactly one of the three approved values.
Use strict vocabulary. No synonyms.
| Verdict | Meaning | Next Action |
|---|---|---|
approved | Implementation is safe to proceed. | auto-execute |
approved_with_risks | Implementation is safe but carries known risks. Document them. | auto-execute |
needs_correction | Plan is flawed or unsafe. Return to planning. | auto-plan |
Add a ## Review: Engineering section to PLAN.md using the exact template in references/review-template.md.
Run sync-status.mjs from this skill's scripts directory.
Update .agent/.automaton/state/current.json:
engineering_review → <verdict>State the next skill based on the verdict.
PLAN.md with appended ## Review: Engineering section.agent/.automaton/state/current.json updated with engineering_review; stage is unchanged by this skillerror-level diagnostics block the review; warning-level diagnostics surface to the next stageapproved or approved_with_risks → auto-execute; needs_correction → auto-plan. The user or host invokes the next skill; auto-eng-review does not chain.needs_correction. Do not guess.canonical_design is null, absent, or intentionally skipped by the plan.Read references/review-template.md for the exact markdown format. (~21 lines: 5-field format covering verdict/strength/concern/action/verified, with rules on sentence limits and no extra commentary.)
Read references/risk-examples.md for sample risk matrices. (~40 lines: 3 scored examples: API migration → approved_with_risks, new external service → needs_correction, refactor → approved.)
Read references/prime-directives.md for 9 non-negotiable standards and preferences. (~35 lines: 9 standards from zero-silent-failures to scrap-it permission; engineering preferences section covering DRY, testing, observability, security, deployment.)
Read references/engineering-sections.md only when the plan carries non-trivial engineering risk. (~160 lines: trigger-based checks for architecture, error/rescue map, security/threat model, data flow/interaction edge cases, code quality, test review, performance, observability, deployment/rollout, long-term trajectory, design/UX.)
Read references/implementation-alternatives.md only when PLAN.md lacks an approach rationale, the user asks for alternatives, or the review verdict depends on comparing safer execution paths. (~25 lines: compact APPROACH format.)
Product go/no-go on a framed spec. Use after auto-frame, before planning.
Implement approved plan slices. Use as the execute-stage entry point.
Bound and de-risk a request into SPEC.md. Use when the objective is clear but scope needs constraining.
Sharpen a vague idea into a bounded objective. Use before framing when scope is undefined.
Build project truth from repo evidence. Use when steering is missing or stale.
Turn an approved spec into ordered slices. Use when framing is accepted and planning begins.