plan-changes

Update PLAN.md in a pull request based on reviewer feedback.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/rom-orlovich/agents-system --skill plan-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-changes
Source: https://github.com/rom-orlovich/agents-system/tree/main/claude-code-cli/agents/planning-agent/skills/plan-changes
Command: npx skills add https://github.com/rom-orlovich/agents-system --skill plan-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates updating the PLAN.md in a pull request when reviewers request changes, reducing manual edits and preserving a clear change history.

Core Features & Use Cases

  • Automatic plan revision: Update the PLAN.md with the revised approach and add an "Addressed Feedback" section.
  • Commit & reply: Commit the updated PLAN.md to the PR branch and post a reviewer-friendly reply summarizing changes.
  • Traceability: Maintain an auditable trail of feedback and corresponding plan updates across iterations.

Quick Start

Use the plan-changes skill to update PLAN.md in response to reviewer feedback on the PR.

Frequently Asked Questions about plan-changes

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

FAQPage Schema
How do I automatically update a PR plan from reviewer feedback?

To automatically update a PR plan from reviewer feedback, this Skill reads PR comments, modifies PLAN.md with the revised approach, and commits changes directly back to the PR branch. It adds an "Addressed Feedback" section and posts a reply summarizing the changes.

What is the best way to track code review changes in PLAN.md?

The best way to track code review changes in PLAN.md is to automate plan revision. This Skill maintains traceability by preserving a clear change history and creating an auditable trail of reviewer feedback and corresponding plan updates across iterations.

How do I commit PLAN.md updates to a PR branch after requested changes?

To commit PLAN.md updates to a PR branch after requested changes, the Skill applies the feedback, modifies the plan, and commits the file to the PR branch. It then posts a reviewer-friendly reply summarizing the applied changes.

Can I automate adding an Addressed Feedback section to my pull request plan?

Yes, you can automate adding an "Addressed Feedback" section to your pull request plan. The Skill reads PR comments, automatically revises the approach in PLAN.md, and appends the section to document how the feedback was addressed.

Does this Skill require any external dependencies to update PR plans?

No, this Skill requires no external dependencies to update PR plans. It operates independently to read PR comments, modify PLAN.md, and commit changes back to the PR branch without additional packages or components.

When should I avoid automating PR plan updates with this approach?

You should avoid automating PR plan updates when feedback requires complex, non-documentation code changes rather than plan revisions. This Skill specifically targets updating PLAN.md in code review scenarios where changes are requested and tracked in the plan file.