s-requirements-review-subagents

Coordinate parallel Gemini and Claude reviews of requirements documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gyarra/cine_medallo_2 --skill s-requirements-review-subagents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s-requirements-review-subagents
Source: https://github.com/gyarra/cine_medallo_2/tree/main/.claude/skills/s-requirements-review-subagents
Command: npx skills add https://github.com/gyarra/cine_medallo_2 --skill s-requirements-review-subagents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Peer-reviewing a requirements document before implementation by coordinating multiple AI reviewers to surface issues and synthesize findings.

Core Features & Use Cases

  • Cross-model review: Gemini and Claude lenses run in parallel to assess Functional and Technical sections.
  • Opt-in Codex: Codex is off by default and can be enabled if needed to draft Technical sections.
  • Synthesized verdict: A moderator aggregates findings by section and severity into a clear, actionable conclusion.

Quick Start

Run the cross-model review workflow on the target requirements document to obtain a consolidated verdict.

Frequently Asked Questions about s-requirements-review-subagents

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

FAQPage Schema
How do I run a cross-model peer review on a requirements document?

To run a cross-model peer review, coordinate parallel Gemini and Claude lenses to assess your requirements document, then synthesize the findings by section and severity into a final verdict with prioritized recommendations.

What is multi-model requirements review and how does it work?

Multi-model requirements review uses Gemini and Claude lenses in parallel to assess completeness, clarity, and risk in Functional and Technical sections, aggregating findings into a consolidated verdict.

Can I use Codex to draft Technical sections during a requirements review?

Yes, Codex can be optionally enabled to draft Technical sections during the requirements review, but it remains off by default while Gemini and Claude lenses run in parallel.

What's the best way to surface gaps and risks in requirements documents?

The best way to surface gaps and risks is coordinating multiple AI reviewers to assess Functional and Technical sections, synthesizing findings by section and severity into actionable recommendations.

Does the cross-model requirements review verify both Functional and Technical sections?

Yes, the cross-model requirements review verifies that Functional and Technical sections are present, assessing completeness, clarity, and risk before producing a final verdict.

What limitations exist when using multiple AI models to review requirements?

A key limitation is that the review workflow relies on parallel Gemini and Claude lenses to synthesize findings, requiring the requirements document to contain distinct Functional and Technical sections for complete assessment.