iterate

Generate versioned delta changes from archived feature specs.

1|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/wonder-zhang/openspec-autodev --skill iterate-wonder-zhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate
Source: https://github.com/wonder-zhang/openspec-autodev/tree/main/skills/iterate
Command: npx skills add https://github.com/wonder-zhang/openspec-autodev --skill iterate-wonder-zhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

迭代开发:基于已完成功能的归档规格进行增量式迭代,支持版本号参数,帮助团队在受控范围内逐步扩展功能。

Core Features & Use Cases

  • 增量迭代:以归档的需求/规格作为起点,对现有实现进行增量修改和扩展。
  • 版本分支化:支持以 vN 为版本号的迭代分支与工作区管理。
  • 自动化工作流:从归档到变更、规格更新、任务清单生成与测试回归,形成端到端的迭代流程。

Quick Start

在 CLAUDE Code 中执行 iterate 命令以对指定特征进行增量迭代。

Frequently Asked Questions about iterate

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

FAQPage Schema
How do I automate incremental feature iteration from archived specs?

Automating incremental feature iteration extracts archived specs, design, and tasks into a new change directory, generating delta changes and versioned proposals to ensure traceability and backward compatibility.

What is versioned proposal generation for iterative development?

Versioned proposal generation for iterative development creates staged iterations (vN) from archived feature specs, applying delta changes to refine completed features while enforcing a non-interactive workflow.

How do I apply delta changes to an existing feature spec without breaking backward compatibility?

Applying delta changes copies archived content into a new change directory under openspec/changes, updating proposal, specs, design, and tasks while managing session state to maintain backward compatibility.

Can I run incremental spec iteration non-interactively in CLAUDE Code?

Incremental spec iteration enforces a non-interactive workflow in CLAUDE Code, executing the iterate command to manage session state under .claude sessions and openspec/changes automatically.

Does incremental spec iteration work without external dependencies?

Incremental spec iteration operates with zero external dependencies, relying solely on archived feature specs and internal session management to generate versioned proposals and task lists.