engineeringlisted

Write an engineering decision / evaluation report — Problem/Context, Options Considered, a mandatory options-vs-criteria Trade-offs comparison table, Decision, Implementation Notes, and Consequences — with optional ANSI/NISO Z39.18 technical-report front/back matter. Use when a team must document a technical decision or evaluation for the engineers who will build or operate the result. Anti-trigger; for a single immutable decision with no mandatory comparison table use adr, for a pre-build alignment narrative built around prose trade-offs rather than a required table use google-design-doc, for product requirements use prd or feature-spec.
modeled-information-format/mif-docs-plugin · ★ 0 · Data & Documents · score 71

Install: claude install-skill modeled-information-format/mif-docs-plugin

# engineering Produces an **engineering decision / evaluation report**: a practitioner-facing document that evaluates concrete options against stated decision drivers, states which one was chosen, and gives the engineers who build or operate the result enough to act. Its center of gravity is the **comparison table** — the report is not conformant without one mapping every candidate option to the decision drivers. This genre follows the general practitioner evaluation-report convention used across engineering organizations, with an additive optional overlay for formal ANSI/NISO Z39.18 technical-report conformance. ## Pattern (industry: practitioner evaluation report, optional Z39.18 overlay) 1. **Problem / Context** — what is being decided or evaluated, and the decision drivers (requirements, constraints, non-functionals) that will judge the options. 2. **Options Considered** — every candidate, described neutrally. 3. **Trade-offs** — a **required** Markdown comparison table mapping options against the stated decision drivers. A report without this table is not a conformant engineering report. 4. **Decision** — the chosen option, stated plainly, with rationale that ties back to the comparison table. 5. **Implementation Notes** — what it takes to build or operate the choice: dependencies, migration steps, risks, rollout, operational concerns. 6. **Consequences** — what becomes easier, what becomes harder, what to revisit. Add an architecture or flow figure