plan-author-review-loop

Name: plan-author-review-loop
Availability: InStock
Author: nanomader

Generate and validate Markdown implementation plans with deterministic checks.

1|Updated May 27, 2026

Search Tags:#git #planning #markdown #risk-assessment #code-review #planning-review

Ready to run

npx skills add https://github.com/nanomader/codex-workflow-skills --skill plan-author-review-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-author-review-loop
Source: https://github.com/nanomader/codex-workflow-skills/tree/main/plan-author-review-loop
Command: npx skills add https://github.com/nanomader/codex-workflow-skills --skill plan-author-review-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, jq, git, codex, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Create, validate, and escalate Markdown-based implementation plans for repository changes, enabling safe, reversible planning with in-band review before any code changes.

Core Features & Use Cases

Owns the slice planning: writes a concise plan with evidence, scope, and tests to support a single slice implementation.
Applies in Lane workflows: used after a lane file selects a slice and before any code changes, to ensure clarity and governance.
Provides deterministic checks: validates plan claims against repo state and records findings with severity, enabling controlled review handoffs.

Quick Start

Provide a proposed change request and let this skill generate a plan draft and readiness review.

Frequently Asked Questions about plan-author-review-loop

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

FAQPage Schema

How do I create an implementation plan for code changes before modifying my repository?▼

Implementation plan creation for code changes is automated by generating a bounded, Markdown-based plan with evidence, scope, and tests before any code is written. This ensures safe, reversible planning with in-band review.

What is a bounded plan review and how does it validate code changes?▼

A bounded plan review validates code change proposals by running deterministic checks against repository state and recording findings with severity levels. This process ensures safety and traceability before implementation begins.

How do I assess risks in a git repository before starting implementation?▼

Risk assessment for git repository changes is handled by evaluating a Markdown plan file against repo state through a plan-review pipeline. It coordinates evidence gathering and records severity findings for controlled review handoffs.

Do I need python3 and jq to run a plan-review pipeline for git changes?▼

Yes, python3 and jq are required dependencies, along with git and codex. These tools support the deterministic checks and evidence gathering needed to validate Markdown implementation plans.

When should I use a Markdown plan file for repository work instead of directly editing code?▼

Use a Markdown plan file when you need safe, reversible planning with in-band review before any code changes. It is essential for coordinating plan drafting, evidence gathering, and risk assessment in lane workflows.

What's the difference between an AI-assisted implementation plan and manual code review?▼

An AI-assisted implementation plan automates drafting, evidence gathering, and deterministic validation against repo state before code changes. Manual code review typically happens after implementation, lacking pre-change scope and risk traceability.