speckit-iterate-apply

Applies a pending speckit iteration to spec artifacts in dependency order.

9|4|Updated May 13, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-iterate-apply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-iterate-apply
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-iterate-apply
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-iterate-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Apply a defined pending speckit iteration to all related spec artifacts, ensuring changes are applied consistently and auditable across the project.

Core Features & Use Cases

  • Load and validate the pending iteration from pending-iteration.md.
  • Apply changes to spec.md, data-model.md, plan.md, tasks.md, quickstart.md, and research.md in dependency order.
  • Record an Iterations entry and remove the pending file upon successful completion.

Quick Start

Review the pending-iteration.md and run this skill to apply the change across all speckit artifacts.

Frequently Asked Questions about speckit-iterate-apply

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

FAQPage Schema
How do I apply a pending spec iteration across all project artifacts?

To apply a pending spec iteration, the skill executes changes across spec.md, data-model.md, plan.md, tasks.md, quickstart.md, and research.md in dependency order. It ensures atomic saves, preserves IDs, and deletes pending-iteration.md on success.

What is the best way to maintain consistency when updating spec management documents?

Maintaining consistency during spec management updates requires applying changes across all related artifacts in dependency order. This ensures modifications to spec.md, data-model.md, and plan.md are applied atomically and auditably.

How does atomic save work when updating multiple spec artifacts?

Atomic saves during spec artifact updates ensure that changes to spec.md, data-model.md, plan.md, tasks.md, quickstart.md, and research.md are applied together as a single transaction, preventing partial updates and preserving IDs.

Do I need a pending-iteration.md file to automate workflow documentation updates?

Yes, a pending-iteration.md file is required to automate workflow documentation updates. The skill loads and validates the pending iteration from this file, applies changes to related artifacts, and removes it on success.

Why does my spec iteration fail to apply across data-model and plan documents?

Spec iteration application fails when changes cannot be validated from pending-iteration.md or when dependency order constraints between spec.md, data-model.md, and plan.md are violated. Atomic saves prevent partial updates.