iterate-plan

Revises existing implementation plans in flow/plans/ based on user feedback and codebase research.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/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/flow/tree/main/.claude/skills/iterate-plan
Command: npx skills add https://github.com/corticalstack/flow --skill iterate-plan-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementation plans become outdated as requirements change, and rewriting them from scratch wastes prior research. This Skill updates an existing plan file in flow/plans/ with surgical edits grounded in actual codebase reality, preserving what still works. ## Core Features & Use Cases - Feedback-Driven Plan Revision: Parses a plan file path plus requested changes, then makes precise edits while maintaining the plan's existing structure and file:line references. - Conditional Codebase Research: Spawns parallel research sub-tasks (codebase-locator, codebase-analyzer, codebase-pattern-finder) only when changes require new technical understanding. - Confirmation Before Editing: Presents an understanding summary and planned modifications for user approval before touching the plan file. - Use Case: After a plan review, a teammate asks to split Phase 2 into backend and frontend phases and add performance success criteria. Invoke the Skill with the plan path and feedback, and it updates phases, scope, and success criteria consistently. ## Quick Start Ask the AI to iterate on the plan at flow/plans/2025-10-16-feature.md by adding a phase for error handling and updating the success criteria.

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 existing implementation plan with new feedback?▼

Invoke /iterate-plan with the plan file path and your feedback, for example adding a phase or changing success criteria. The Skill reads the full plan, optionally researches the codebase, confirms the intended changes with you, then makes precise edits.

How to split a plan phase into multiple phases without rewriting everything?▼

Provide the plan path and a request like splitting Phase 2 into backend and frontend phases. The Skill edits only the affected sections, keeps the existing phase pattern, and updates scope and success criteria for consistency.

Does iterating a plan require re-researching the codebase?▼

Only when the requested change needs new technical understanding. The Skill spawns research sub-tasks such as codebase-locator or codebase-analyzer for those cases; simple wording or scope edits proceed without research.

What happens if I run iterate-plan without a plan file path?▼

The Skill asks which plan you want to update and suggests listing recent plans with ls -lt flow/plans/. Once you provide the path, it asks for the specific changes before proceeding.

When should I create a new plan instead of iterating an existing one?▼

Iterate when the core approach and most phases remain valid and you need targeted changes. If the entire approach, scope, or architecture is being replaced, creating a fresh plan avoids carrying over outdated structure and assumptions.