iterating-plans

Name: iterating-plans
Availability: InStock
Author: ReadyStateChange

Iterate on specification-first implementation plans while preserving contract integrity.

Updated Mar 8, 2026

Search Tags:#planning #brainstorming #specification #plan #contract #iterate

Ready to run

npx skills add https://github.com/ReadyStateChange/agents --skill iterating-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iterating-plans
Source: https://github.com/ReadyStateChange/agents/tree/main/skills/iterating-plans
Command: npx skills add https://github.com/ReadyStateChange/agents --skill iterating-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterating on existing specification-first implementation plans to incorporate feedback while preserving contract integrity and preventing drift.

Core Features & Use Cases

Facilitates targeted plan updates based on user feedback without changing the underlying contract.
Guides researchers and engineers to align plans with linked specifications, ensuring traceability.
Real-world scenario: after stakeholder review, revise phase scopes and testing criteria to keep the plan aligned with the approved spec.

Quick Start

Update the current plan to reflect the latest feedback while preserving the canonical contract.

Frequently Asked Questions about iterating-plans

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

FAQPage Schema

How do I update an implementation plan after stakeholder feedback without causing contract drift?▼

To update an implementation plan without contract drift, apply targeted plan changes that preserve the canonical structure and maintain alignment to the approved specification, ensuring traceable edits across scope, sequencing, and testing strategies.

How do I adjust the scope and testing criteria of a specification-first plan?▼

You adjust the scope and testing criteria of a specification-first plan by applying contract-preserving edits that revise phase scopes while preserving the canonical structure and maintaining alignment to the approved spec.

When do I need to iterate on an existing implementation plan?▼

You need to iterate on an existing implementation plan when user feedback requires targeted plan changes, such as adjusting phase scopes, sequencing, or testing strategies, while ensuring the updates remain traceable and aligned with the approved specification.

Can I incorporate brainstorming feedback into a plan without altering the underlying specification?▼

Yes, you can incorporate brainstorming feedback through explicit brainstorming-guided approvals that apply contract-preserving edits to the plan, preventing drift while keeping the underlying specification completely unchanged.

What is the best way to preserve testing alignment when modifying implementation phases?▼

The best way to preserve testing alignment during phase modifications is to apply targeted plan changes that explicitly maintain testing alignment with the approved spec, ensuring traceable updates across all adjusted phases.