gsd-plan-review-convergence

Repeatedly replan and review project plans until no HIGH concerns remain.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-plan-review-convergence-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plan-review-convergence
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-plan-review-convergence
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-plan-review-convergence-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents low-quality plans from persisting by repeatedly re-planning and re-reviewing until only acceptable risk remains, specifically removing any remaining HIGH concerns before proceeding.

Core Features & Use Cases

  • Cross-AI external review loop: Runs plan review with selectable AI CLI reviewers (e.g., Codex, Gemini, Claude, OpenCode) and optionally local model servers (Ollama, LM Studio, llama.cpp).
  • Replan with targeted review feedback: When HIGH concerns are detected, it re-invokes the planning phase using the --reviews feedback to drive convergence.
  • Controlled convergence safeguards: Enforces workflow gates, revision-loop behavior, stall detection, and escalation boundaries, stopping when no HIGH concerns remain or when --max-cycles is reached.
  • Use Case: You generate an engineering plan, have multiple AI reviewers check it for high-risk issues, and automatically iterate until the remaining issues are no longer classified as HIGH.

Quick Start

Use gsd-plan-review-convergence with a specific phase number by running it as gsd-plan-review-convergence <phase> --codex --max-cycles 3.

Frequently Asked Questions about gsd-plan-review-convergence

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

FAQPage Schema
How do I automate AI code review for iterative planning until high-risk concerns are resolved?

Automating AI code review for iterative planning requires a convergence loop that repeatedly executes plan reviews and re-invokes the planning phase using review feedback until no HIGH concerns remain or a maximum cycle limit is reached.

What is a replanning loop for risk triage and how does it work?

A replanning loop for risk triage continuously evaluates project plans through external reviewer CLIs, detecting HIGH concerns and feeding the review feedback back into the planning phase to converge on an acceptable risk state.

Can I use local model servers like Ollama or LM Studio for cross-AI plan review?

Yes, you can use local OpenAI-compatible model servers like Ollama, LM Studio, or llama.cpp alongside selectable AI CLI reviewers such as Codex, Gemini, or Claude to execute the cross-AI external review loop.

How do I set workflow gating limits for automated plan revision cycles?

You configure workflow gating limits by specifying a phase number and setting the max-cycles parameter, which enforces revision-loop behavior, stall detection, and escalation boundaries to stop the convergence loop safely.

Why does my automated planning loop stall during risk triage?

Automated planning loops stall during risk triage when the workflow gating safeguards detect a lack of convergence progress or when the maximum cycle limit is reached before eliminating all HIGH concerns from the plan.

When should I use an external review-driven replanning loop instead of manual plan checks?

Use an external review-driven replanning loop when you need to enforce strict quality-gating workflows across development cycles, ensuring that automated cross-AI review feedback systematically eliminates HIGH risk concerns that manual checks might miss.