speckit-iterate-define

Name: speckit-iterate-define
Availability: InStock
Author: OpsMill

Generate a pending iteration plan from a change request, specifying affected artifacts and tasks without altering them.

9|4|Updated May 13, 2025

Search Tags:#git #planning #documentation #specification #tasks #iterate #feature-iteration

Ready to run

npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-iterate-define

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-iterate-define
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-iterate-define
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-iterate-define

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams codify and manage feature iteration work by converting a change request into a structured, reviewable plan that aligns spec, plan, and tasks.

Core Features & Use Cases

Generates a pending iteration plan based on current feature state and user input.
Assesses implementation progress against tasks and phase boundaries to ensure realistic planning.
Produces a ready-to-apply change proposal that preserves completed work and flags risks.

Quick Start

Provide a change request to generate a pending iteration plan.

Frequently Asked Questions about speckit-iterate-define

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

FAQPage Schema

How do I generate a feature iteration plan from a change request?▼

To generate a feature iteration plan, provide a change request and the system will produce a pending plan capturing scope, artifacts affected, and tasks impacted without altering existing artifacts during the planning step.

What is a pending iteration plan in feature development?▼

A pending iteration plan is a structured, reviewable proposal that aligns spec, plan, and tasks based on the current feature state, preserving completed work and flagging risks before any changes are applied.

How do I plan feature iterations without altering existing specifications and tasks?▼

You can plan feature iterations without altering existing artifacts by generating a pending iteration plan that captures the scope and impacted tasks first, applying the concrete changes only when you are ready to execute the iteration.

Can I assess implementation progress against tasks before creating an iteration plan?▼

Yes, the system assesses implementation progress against tasks and phase boundaries to ensure realistic planning, producing a ready-to-apply change proposal that reflects current feature progress.

What is the best way to codify feature iteration work into a reviewable plan?▼

The best way to codify feature iteration work is converting a change request into a structured plan that aligns spec, plan, and tasks while flagging risks and preserving completed work for team review.

Does the iteration planning process modify my current feature artifacts?▼

No, the iteration planning process does not modify your current feature artifacts during the planning step; it only generates a pending plan with concrete proposed changes to spec, plan, and tasks for review.