benchmark-plan-reviewer

Review benchmark planner handoffs for physical feasibility of payload trajectories.

2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/MRiabov/Problemologist-AI --skill benchmark-plan-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark-plan-reviewer
Source: https://github.com/MRiabov/Problemologist-AI/tree/main/.agents/skills/benchmark-plan-reviewer
Command: npx skills add https://github.com/MRiabov/Problemologist-AI --skill benchmark-plan-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews benchmark planners' handoffs to verify that payload trajectories and operating assumptions are physically satisfiable from the full plan, preventing downstream infeasibility.

Core Features & Use Cases

  • Review planner handoffs for consistency across artifacts and evidence.
  • Validate payload trajectory feasibility against anchors, DOFs, and timing windows.
  • Produce stage-scoped benchmark-plan review manifests and actionable feedback.

Quick Start

Open the latest planner artifacts, perform the standard review checks, and publish the stage-scoped decision under reviews/.

Frequently Asked Questions about benchmark-plan-reviewer

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

FAQPage Schema
How do I verify physical feasibility of a payload trajectory before finalizing the benchmark plan?

Validate payload trajectory feasibility by reviewing benchmark planner handoffs against motion, timing, and geometry constraints to ensure physical satisfiability and prevent downstream infeasibility.

What is cross-artifact validation for benchmark planner handoffs?

Cross-artifact validation checks consistency across benchmark_plan.md, benchmark_definition.yaml, and assembly definitions to ensure payload trajectories and operating assumptions are physically satisfiable from the full plan.

How do I review payload trajectory definitions against timing windows and degrees of freedom?

Validate payload trajectory definitions against anchors, degrees of freedom, and timing windows by enforcing explicit motion and geometry constraints to produce compliant review decisions.

Does the benchmark plan review process require specific assembly definition files?

Yes, the benchmark plan review process requires benchmark_assembly_definition.yaml and payload_trajectory_definition.yaml to cross-validate physical feasibility and operating assumptions across artifacts.

What's the best way to produce compliant review manifests for benchmark plans?

Produce compliant review manifests by enforcing explicit motion, timing, and geometry constraints with evidence, generating stage-scoped decisions under the reviews directory.

Why does my benchmark plan fail physical feasibility checks during payload trajectory review?

Benchmark plans fail physical feasibility checks when payload trajectories violate explicit motion, timing, or geometry constraints, requiring actionable feedback to resolve inconsistencies across artifacts.