rpi-iterate

Updates existing implementation plans based on feedback with codebase research.

5|Updated Sep 24, 2017
One-click install
npx skills add https://github.com/madyankin/dotfiles --skill rpi-iterate-madyankin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rpi-iterate
Source: https://github.com/madyankin/dotfiles/tree/main/.config/agents/skills/rpi-iterate
Command: npx skills add https://github.com/madyankin/dotfiles --skill rpi-iterate-madyankin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementation plans often need revision after review, but ad-hoc edits risk inconsistency, stale file references, and unverified assumptions. This Skill provides a disciplined workflow for modifying existing plan files so every change is grounded in actual codebase reality. ## Core Features & Use Cases - Feedback-Driven Plan Updates: Reads the entire existing plan, parses requested changes, and applies surgical edits while preserving structure and file:line references. - Research-Backed Changes: Spawns parallel research agents (codebase locator, analyzer, pattern finder) when feedback requires new technical understanding before editing. - Confirmation Workflow: Presents understanding and planned modifications for user approval before touching the plan file. - Use Case: A reviewer asks to add a caching phase to a plan in _scratchpad/plans/. The Skill researches existing cache patterns in the codebase, confirms the approach, then inserts a new phase following the plan's existing format with updated success criteria. ## Quick Start Update the plan in _scratchpad/plans/ based on my feedback about adding error handling to the authentication phase.

Frequently Asked Questions about rpi-iterate

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

FAQPage Schema
How do I update an existing implementation plan with new feedback?▼

Provide your feedback describing what to add, modify, or remove in the plan file. The Skill reads the entire plan, researches the codebase if needed, confirms its understanding with you, then makes surgical edits while preserving the existing structure.

How to revise a plan without losing existing structure?▼

The Skill makes focused, precise edits rather than wholesale rewrites. It maintains the existing format, keeps file:line references accurate, and follows established patterns when adding new phases or sections.

Does plan updating verify changes against the actual codebase?▼

Yes. When feedback requires new technical understanding, the Skill spawns parallel research agents to locate relevant files, analyze implementation details, and find similar patterns before making any edits.

When should I use plan iteration instead of writing a new plan?▼

Use iteration when an existing plan needs refinement, scope changes, or extensions based on review feedback. Write a new plan only when the original is fundamentally obsolete or the task has changed entirely.

What happens if my feedback is vague or raises questions?▼

The Skill asks clarifying questions before updating rather than guessing. It confirms its understanding of your requested changes and planned modifications, and only proceeds after your approval.