amend-plan

Revise implementation plans by adjusting plan files, rewriting commits, and force-pushing branches.

2|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/vintasoftware/vinta-schedule-frontend-web --skill amend-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amend-plan
Source: https://github.com/vintasoftware/vinta-schedule-frontend-web/tree/main/.claude/skills/amend-plan
Command: npx skills add https://github.com/vintasoftware/vinta-schedule-frontend-web --skill amend-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill empowers you to make adjustments to existing implementation plans after work has started, ensuring seamless updates and maintaining the integrity of the project's history.

Core Features & Use Cases

  • Plan Revision: Modify existing phases or append new ones to the plan.
  • History Rewriting: Automatically adjust commits and force-push branches to reflect changes.
  • Review and Validation: Ensures every change is reviewed and validated before execution.
  • Use Case: When a new requirement arises or a phase needs to be rewritten, use this Skill to update the plan and ensure all related changes are applied correctly.

Quick Start

Use the amend-plan skill to update the phase "Phase 2" in the plan "Feature X Plan" and append a new phase "Phase 3".

Frequently Asked Questions about amend-plan

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

FAQPage Schema
How do I revise an implementation plan after development has already started?

To revise an implementation plan, you modify existing phases or append new ones to the plan file. The process ensures seamless updates and maintains project history integrity after work has started.

Can I rewrite Git commits and force-push branches when changing a project plan?

Yes, history rewriting is supported. The process automatically adjusts commits and force-pushes branches in a controlled manner to reflect the changes made to your implementation plan.

What is the best way to safely append new phases to an active implementation plan?

The safest way to append new phases is through a controlled revision process that ensures every plan change is reviewed and validated before execution against your Git and PR systems.

Does amending a plan require coordination with Git and PR systems?

Yes, amending a plan requires coordination with Git and PR systems. This integration is necessary to validate the changes and execute the required history rewriting and branch force-pushing.

When do I need to force-push branches to update an implementation plan?

You need to force-push branches when a new requirement arises or an existing phase needs rewriting. This action applies the updated plan changes correctly to the project's commit history.

Are there limitations when rewriting commits to reflect implementation plan changes?

The primary limitation is that history rewriting and force-pushing alter the existing commit history. To mitigate risks, the process enforces strict review and validation before executing any branch changes.