aget-review-project

Assess gate progress and V-test completion from PROJECT_PLAN files.

1|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-review-project-gmelli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aget-review-project
Source: https://github.com/gmelli/public-OpenAI-DeepResearch-aget/tree/main/.claude/skills/aget-review-project
Command: npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-review-project-gmelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assess ongoing project plans for gate progress, V-test completion, blockers, and risk exposure so teams can take timely corrective actions and prioritize work to meet success criteria.

Core Features & Use Cases

  • Gate and V-test Evaluation: Parses PROJECT_PLAN files to enumerate gates, extract V-tests, classify status markers (passed/failed/pending/in_progress), and compute completion metrics.
  • Blocker & Risk Identification: Detects failed V-tests, blocked items, dependencies, and risks flagged as materialized to surface true impediments to progress.
  • Actionable Recommendations: Produces prioritized next steps, scope adjustments, and risk alerts to guide immediate remediation and decision-making.
  • Use Case: Run a mid-flight review on an active engineering project plan to determine which gates are blocking release and produce a recommended remediation plan for the PO and POC.

Quick Start

Ask the agent to review the project plan at planning/PROJECT_PLAN_<name>.md for gate progress, V-test results, blockers, and actionable recommendations.

Frequently Asked Questions about aget-review-project

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

FAQPage Schema
How do I assess mid-flight project health and V-test completion?

To assess mid-flight project health, you need to parse active project plan files to evaluate gate progress, enumerate V-tests, classify status markers, and identify materialized blockers. This generates a structured progress report for course correction.

How do I identify blockers and materialized risks in a project plan?

Identifying blockers and materialized risks involves parsing project plans to detect failed V-tests, blocked items, and flagged dependencies. Surfacing these true impediments allows teams to generate prioritized recommendations for immediate remediation.

Can I generate actionable recommendations for course correction from a project plan?

Generating actionable recommendations for course correction requires analyzing gate progress and risk exposure in project plans. The process outputs prioritized next steps, scope adjustments, and risk alerts to guide immediate decision-making.

Does a gate review require specific status markers in the project plan file?

A gate review requires project plan files containing gate and V-test markers along with status indicators. The assessment parses these passed, failed, pending, or in_progress markers to compute completion metrics and identify blocked release items.

What is the best way to run a mid-flight project review for an active engineering project?

The best way to run a mid-flight project review is to apply read-only analysis to active PROJECT_PLAN files. This evaluates gate progress, extracts V-test results, and produces a recommended remediation plan for project owners.

What are the limitations of automated gate progress evaluation?

Automated gate progress evaluation is limited to parsing existing markers within project plan files. It cannot assess unrecorded risks or external blockers, requiring read-only access to structured plan data to output accurate completion metrics.