plan-script

Generate step-by-step execution plans with target files, metrics, and rollback strategies.

1|1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/csuzngjh/principles --skill plan-script
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-script
Source: https://github.com/csuzngjh/principles/tree/main/claude/skills/plan-script
Command: npx skills add https://github.com/csuzngjh/principles --skill plan-script

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill generates a clear, step-by-step execution plan for a given task, ensuring controlled and verifiable operations.

Core Features & Use Cases

  • Structured Planning: Creates detailed plans including target files, execution steps, verification metrics, and rollback strategies.
  • Controlled Operations: Ensures that modifications are authorized and that there's a clear path to revert changes if necessary.
  • Use Case: Before making significant changes to a codebase, use this Skill to generate a plan that lists exactly which files will be modified, how to verify the changes, and how to undo them if something goes wrong.

Quick Start

Update the plan in docs/PLAN.md and set its status to READY.

Frequently Asked Questions about plan-script

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

FAQPage Schema
How do I generate an execution plan with a rollback strategy for codebase changes?

To generate an execution plan with a rollback strategy, this skill structures target files, operational steps, quantifiable success metrics, and failure recovery actions into a movie-script format for controlled task execution.

What is a movie-script style execution plan for task management?

A movie-script style execution plan is a detailed step-by-step document specifying target modifications, expected intermediate states, and verification metrics to ensure controlled and verifiable codebase operations.

How do I verify intermediate states during a codebase modification task?

You verify intermediate states during codebase modification by defining quantifiable success metrics within the execution plan, allowing you to check expected outcomes after each operational step before proceeding.

Can I use this to plan file modifications without a dedicated testing framework?

Yes, you can plan file modifications without a dedicated testing framework because the skill relies on defining quantifiable success metrics and rollback strategies directly within the generated execution plan.

What is the best way to document a rollback strategy before modifying target files?

The best way to document a rollback strategy is to generate a structured execution plan that explicitly outlines the steps to revert changes if the quantifiable success metrics indicate a failure scenario.