eng-review

Automate architecture and engineering reviews with diagrams, state models, and test matrices.

11|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/KSD-CO/IronCode --skill eng-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-review
Source: https://github.com/KSD-CO/IronCode/tree/main/.ironcode/skill/eng-review
Command: npx skills add https://github.com/KSD-CO/IronCode --skill eng-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides an explicit, repeatable engineering review process that locks in architecture, data flow, state models, failure modes, edge cases, security boundaries, and a test matrix before implementation.

Core Features & Use Cases

  • Architecture diagrams: ASCII maps of components, data flow, and trust boundaries.
  • State model definitions: Clear states, transitions, triggers, visibility, and persistence.
  • Risk, security, and testing: Structured failure modes, edge-case coverage, secure design considerations, and a comprehensive test matrix.
  • Implementation planning: Named files and package ownership to guide rollout.

Quick Start

Produce an architecture review with diagrams and an implementation plan.

Frequently Asked Questions about eng-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I formalize architecture diagrams and state models before starting implementation?

Architecture diagrams and state models are formalized by applying a structured engineering review process that defines component maps, data flow, state transitions, and trust boundaries. This locks in design decisions before any code is written.

What is the best way to document failure modes and security boundaries for complex software?

The best way to document failure modes and security boundaries is through an engineering review that systematically identifies risk analysis, edge-case coverage, and secure design considerations alongside a comprehensive test matrix.

How do I create an implementation plan with named files and package ownership?

An implementation plan with named files and package ownership is created by finalizing architecture diagrams, state models, and test matrices first, then mapping concrete rollout responsibilities to specific code packages.

When do I need a formal engineering review for my software initiative?

A formal engineering review is needed for complex software initiatives requiring diagrams, data-flow definitions, failure modes, and security boundaries to lock in design decisions before implementation begins.

Does this engineering review process support defining state transitions and triggers?

Yes, the engineering review process supports defining state models by detailing clear states, transitions, triggers, visibility rules, and persistence mechanisms to ensure robust state management.

Can I use ASCII diagrams for component mapping and trust boundaries in an architecture review?

Yes, ASCII diagrams can be used to map components, illustrate data flow, and define trust boundaries, providing a clear and portable visual representation within the engineering review documentation.