review-plan

Name: review-plan
Availability: InStock
Author: potenlab

Edits existing plan documents sequentially and appends a Revision Log after changes.

2|Updated Jan 24, 2026

Search Tags:#workflow #documentation #review #project-planning #team-collaboration #plan-edit #revision-log

Ready to run

npx skills add https://github.com/potenlab/marketplace-potenlab --skill review-plan-potenlab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/potenlab/marketplace-potenlab/tree/main/plugins/potenlab-workflow/skills/review-plan
Command: npx skills add https://github.com/potenlab/marketplace-potenlab --skill review-plan-potenlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams update and refine existing plan documents (ui-ux-plan.md, dev-plan.md, frontend-plan.md, backend-plan.md) based on user feedback, preserving prior work and ensuring consistency.

Core Features & Use Cases

Orchestrates the end-to-end edit flow: ui-ux-specialist, tech-lead-specialist, and frontend/backend specialists in parallel where applicable.
Verifies required plan files exist before edits and appends a Revision Log after changes.
Updates progress.json if it exists and provides a final change report.

Quick Start

Invoke /review-plan with your feedback (or provide feedback via AskUserQuestion) to edit the existing plan files in sequence and update progress tracking.

Frequently Asked Questions about review-plan

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

FAQPage Schema

How do I edit existing project plan documents based on user feedback?▼

You can edit existing project plan documents by applying feedback sequentially across ui-ux, tech-lead, and parallel frontend/backend plans, appending a revision log and updating progress tracking.

What is the workflow for updating UI UX plan and dev plan files with revisions?▼

The workflow for updating plan files follows a sequential flow: ui-ux-plan.md first, then tech-lead dev-plan.md, then parallel frontend-plan.md and backend-plan.md edits, ending with a revision log.

Do I need existing plan files to run a plan revision workflow?▼

Yes, you need existing plan files. The workflow verifies required plan documents like frontend-plan.md and backend-plan.md exist before applying edits to preserve prior work.

How does progress tracking work when refining a development plan?▼

Progress tracking works by updating progress.json if it exists, logging applied changes and providing a final change report after the plan revision workflow completes.

Can I update frontend and backend plans at the same time during a plan edit?▼

Yes, you can update frontend and backend plans at the same time. The edit workflow processes frontend-plan.md and backend-plan.md in parallel after sequential ui-ux and tech-lead edits.

What's the best way to maintain consistency across project planning documents?▼

The best way to maintain consistency across project planning documents is orchestrating an end-to-end edit flow that preserves prior work and appends a revision log after changes.