revise

Apply user feedback to refine implementation plan files with surgical edits.

581|102|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill revise-juicesharp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revise
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/revise
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill revise-juicesharp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update and refine existing implementation plans based on feedback, performing surgical edits to preserve structure and quality while staying aligned with codebase reality.

Core Features & Use Cases

  • Plan-path validation: Identifies and validates the target plan path and detects if a review artifact path was provided, ensuring correct targets.
  • Contextual edits: Applies feedback as precise, surgical modifications to plan content, preserving original structure.
  • Guardrails: Prompts for clarification on ambiguous feedback and handles edge cases (no plan path or feedback-only inputs).
  • Use Case: When a review reveals issues in a plan, revise updates the plan accordingly and preserves structure.

Quick Start

Provide the target plan path and the feedback text to apply to update the plan.

Frequently Asked Questions about revise

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

FAQPage Schema
How do I edit an implementation plan based on review feedback without losing the original structure?

To edit an implementation plan based on review feedback without losing structure, apply surgical modifications that preserve the original formatting. This ensures precise updates align with codebase reality while maintaining document integrity during iterative refinement.

What is the best way to automate iterative refinement of an existing workflow plan?

Automating iterative refinement of an existing workflow plan involves parsing user feedback and applying targeted modifications to the target plan file. This process enforces guardrails to detect ambiguous or incorrect changes during implementation updates.

How do I handle ambiguous feedback when updating planning documents?

When updating planning documents, handling ambiguous feedback requires built-in guardrails that prompt for clarification. This prevents incorrect changes by validating the target plan path and ensuring feedback instructions are precise before modifying plan content.

Can I apply specific modifications to a plan file if no review artifact is provided?

Yes, you can apply modifications to a plan file with feedback-only inputs, though the system validates for review artifact paths to ensure correct targets. It handles edge cases by processing direct feedback against the specified plan path.

What are the limitations of automated plan editing when resolving codebase issues?

Automated plan editing for codebase issues is limited by its dependency on clear feedback; if instructions are ambiguous, the system pauses to prompt for clarification. It requires a valid target plan path to function correctly.