plan-eng-review

Audit engineering design documents for structural completeness and failure-mode coverage.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/mihai-chiorean/inc --skill plan-eng-review-mihai-chiorean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/mihai-chiorean/inc/tree/main/skills/plan-eng-review
Command: npx skills add https://github.com/mihai-chiorean/inc --skill plan-eng-review-mihai-chiorean

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent and shallow design documentation reviews by enforcing a rigorous, multi-layered audit process that ensures structural integrity and architectural soundness.

Core Features & Use Cases

  • Mechanical Validation: Automatically checks for required sections, missing stubs, and valid frontmatter status transitions.
  • Qualitative Analysis: Evaluates architecture, failure-mode registries, test coverage, and diagram staleness using expert-level heuristics.
  • Lifecycle Management: Handles status updates, telemetry logging, and restore-point snapshots upon successful audit completion.

Quick Start

Invoke the plan-eng-review skill by asking the agent to audit your specific design document file path.

Frequently Asked Questions about plan-eng-review

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

FAQPage Schema
How do I automate a qualitative audit for engineering design docs?

To automate a qualitative audit for engineering design docs, use a skill that performs mechanical validation and qualitative analysis to ensure architectural coherence and structural completeness. This process checks required sections, failure-mode registries, and test coverage standards.

What is mechanical validation for design document reviews?

Mechanical validation for design document reviews is an automated process that checks for required sections, missing stubs, and valid frontmatter status transitions. It enforces structural integrity before applying deeper qualitative analysis to architecture and test coverage.

Do I need a structured scaffold to review architecture and failure-mode registries?

Yes, you need a structured design doc scaffold to review architecture and failure-mode registries. The audit process requires this structured input alongside the plan-eng-review-audit binary to execute validation and mutation tasks successfully.

Can I use automated quality assurance to check diagram staleness in technical planning?

Yes, you can use automated quality assurance to check diagram staleness during technical planning. The audit evaluates diagram staleness using expert-level heuristics alongside architecture coherence and failure-mode registry validation.

How do I handle lifecycle management and status updates after a design doc review?

To handle lifecycle management after a design doc review, the audit process automatically manages status updates, telemetry logging, and restore-point snapshots upon successful completion. This ensures your technical planning documents maintain valid state transitions.

What are the limitations of automated engineering design doc audits?

Limitations of automated engineering design doc audits include dependency on a structured scaffold and the plan-eng-review-audit binary for execution. The audit cannot validate content outside this structure and relies on expert-level heuristics rather than human contextual judgment.