optimus-review

Validate completed tasks against specs, standards, security, and tests via parallel agents.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/alexgarzao/optimus --skill optimus-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimus-review
Source: https://github.com/alexgarzao/optimus/tree/main/review/skills/optimus-review
Command: npx skills add https://github.com/alexgarzao/optimus --skill optimus-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that a completed task satisfies specification, coding standards, security practices, and production readiness by orchestrating parallel expert assessments, reducing rework and speeding PR readiness.

Core Features & Use Cases

  • Parallel agents evaluate code quality, business logic, security, and test coverage after a build finishes.
  • Interactive findings flow guides resolution and decision-making before PR review or task closure.
  • Supports explicit task IDs or auto-detection, dependency awareness, and integration with existing task state and metadata.

Quick Start

Provide a completed task ID to validate (e.g., T-012) and run the post-task validation workflow to dispatch agents and report findings.

Frequently Asked Questions about optimus-review

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

FAQPage Schema
How do I automate spec compliance and code review after a task build?

Automated post-task validation dispatches parallel expert agents to evaluate spec compliance, coding standards, security, and test coverage. You provide a TaskSpec, reference docs, and a Makefile with lint and test targets to gate execution and report findings.

What do I need to run automated QA validation on full-stack changes?

Automated QA validation requires a completed TaskSpec, reference documentation, and a Makefile containing lint and test targets to gate execution. The workflow applies after a build completes and uses these inputs to dispatch specialized review agents.

Can I use parallel agents to check security and test coverage before a PR?

Parallel agents evaluate code quality, business logic, security practices, and test coverage simultaneously. The interactive findings flow guides resolution and decision-making before PR review or task closure, reducing rework and speeding readiness.

Does the validation workflow support explicit task IDs and dependency awareness?

The validation workflow supports explicit task IDs like T-012 or auto-detection, dependency awareness, and integration with existing task state and metadata. Provide a completed task ID to validate and run the post-task workflow to dispatch agents.

What is the best way to validate production readiness for a completed task?

The best way to validate production readiness is orchestrating parallel expert assessments that check specification compliance, coding standards, security practices, and test coverage. This reduces rework and speeds PR readiness by resolving findings interactively.

When should I not use automated post-task validation for code review?

Automated post-task validation should not be used without a TaskSpec, reference docs, or a Makefile with lint and test targets. It applies after a build completes for re-validation requests on full-stack changes with dependencies.