engineer-plan-reviewer

Validate engineering plan artifacts against stage manifests and motion-trajectory contracts.

2|Updated Jan 31, 2026

Search Tags:#validation #evidence #review #engineering #manifests #trajectory #cad

Ready to run

npx skills add https://github.com/MRiabov/Problemologist-AI --skill engineer-plan-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: engineer-plan-reviewer
Source: https://github.com/MRiabov/Problemologist-AI/tree/main/.agents/skills/engineer-plan-reviewer
Command: npx skills add https://github.com/MRiabov/Problemologist-AI --skill engineer-plan-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured review workflow for engineering plans and execution artifacts, ensuring plan fidelity, manufacturability, and safety constraints are satisfied.

Core Features & Use Cases

Enforces manifest-compliant plan reviews and execution handoffs across the engineering lifecycle.
Validates simulation evidence, renders, and trajectory-grounding against formal motion contracts.
Use Case: teams verifying engineering_plan.md, todo.md, benchmark_definition.yaml, assembly_definition.yaml, or solution_script.py before manufacturing or deployment.

Quick Start

Run the Engineer Plan Reviewer on the latest engineering_plan.md to produce a stage-specific verdict.

Frequently Asked Questions about engineer-plan-reviewer

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

FAQPage Schema

How do I validate an engineering plan against stage manifests and motion trajectory contracts?▼

To validate an engineering plan, you review engineering_plan.md, todo.md, and assembly_definition.yaml against explicit stage manifests, verifying plan fidelity, inventory grounding, and enforcing formal motion-trajectory proofs before approval.

What files are required to review engineering execution handoffs and simulation evidence?▼

Reviewing engineering execution handoffs requires benchmark_definition.yaml, assembly_definition.yaml, solution_plan_evidence_script.py, validation_results.json, and simulation_result.json to verify evidence integrity and trajectory grounding.

Does the engineering plan review process require media previews before approval?▼

Yes, the engineering plan review process requires formal motion and trajectory previews, along with required media inspection, to ensure manufacturability and safety constraints are satisfied before granting approval.

How do I check engineering plan fidelity and inventory grounding before manufacturing?▼

Checking engineering plan fidelity involves validating the engineering_plan.md and todo.md against assembly_definition.yaml to ensure inventory grounding and evidence integrity are satisfied before deployment or manufacturing.

What is the best way to enforce formal motion trajectory proofs in engineering plan reviews?▼

The best way to enforce formal motion trajectory proofs is by validating simulation_result.json and validation_results.json against explicit stage manifests, ensuring trajectory-grounding constraints are met before final approval.

Can I use this review workflow to validate solution plan evidence scripts?▼

Yes, this review workflow validates solution_plan_evidence_script.py to verify evidence integrity, ensuring the script's outputs align with benchmark_definition.yaml and motion trajectory contracts before manufacturing.