iterate-plan

Revise existing implementation plans with user feedback and codebase research.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/claude-code-flow --skill iterate-plan-corticalstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate-plan
Source: https://github.com/corticalstack/claude-code-flow/tree/main/.claude/skills/iterate-plan
Command: npx skills add https://github.com/corticalstack/claude-code-flow --skill iterate-plan-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you update an existing implementation plan so the next development steps match real feedback, while avoiding vague or incorrect changes by re-checking assumptions against the codebase when needed.

Core Features & Use Cases

  • Plan iteration from an existing file: Reads the full current plan and applies only the specific requested adjustments (e.g., scope, phases, or success criteria).
  • Research only when required: Spawns targeted research subtasks when the feedback implies new technical understanding or needs validation against actual repository patterns.
  • Guardrailed, interactive updates: Confirms understanding with you before editing, then makes focused edits that preserve plan structure and measurement quality.

Quick Start

Use the iterate-plan skill to revise an existing plan file after you share the exact feedback, like: Provide the path to your plan under flow/plans and describe what you want to change.

Frequently Asked Questions about iterate-plan

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

FAQPage Schema
How do I update an implementation plan based on new feedback without losing alignment to the codebase?

Implementation plan updates incorporate feedback by fully reading the existing plan, conditionally researching the codebase via parallel subtasks, confirming changes, and applying surgical edits to scope, phases, or success criteria.

What is the best way to revise success criteria in an existing development plan?

Revising success criteria requires a surgical, consistency-preserving modification process that reads the full plan, validates technical assumptions against repository patterns, and confirms adjustments before editing the plan file.

How do I adjust project scopes and phases in a plan file after receiving user feedback?

Adjusting scopes and phases involves reading the existing plan file, spawning targeted research subtasks if feedback requires new technical understanding, and making focused edits that preserve the overall plan structure.

Do I need to manually research the codebase before iterating on my implementation plan?

Manual codebase research is not always required; the plan iteration process spawns targeted parallel research subtasks automatically only when feedback implies new technical understanding or needs validation against actual repository patterns.

Can I apply changes to plan files outside of the standard planning workflow directory?

Plan iteration specifically targets updating plan files located in the flow/plans directory during manual and explicit planning workflows, ensuring changes are consistently applied within the established repository structure.