iterate-on-plan

Analyze and update OpenSpec proposal documents by severity thresholds.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill iterate-on-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate-on-plan
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/iterate-on-plan
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill iterate-on-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill addresses the need to systematically improve OpenSpec proposals by identifying and fixing issues related to completeness, clarity, feasibility, scope, consistency, testability, parallelizability, and hidden assumptions.

Core Features & Use Cases

  • Iterative Analysis: Repeatedly scans proposal documents and generates structured findings.
  • Automated Fixes: Applies corrections to proposal, tasks, design, and spec files based on severity thresholds.
  • Parallel Review: Optionally dispatches multi‑vendor reviews and integrates consensus findings.
  • Coordinator Integration: Detects and leverages a coordination layer for handoff, memory, and guardrails when available.

Quick Start

Use the iterate-on-plan skill with a change ID to automatically refine the proposal.

Frequently Asked Questions about iterate-on-plan

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

FAQPage Schema
How do I improve OpenSpec proposal quality and fix completeness issues?

To refine OpenSpec proposals, use iterative analysis that repeatedly scans documents for hidden assumptions and scope inconsistencies, then applies automated corrections to proposal, tasks, design, and spec files based on severity thresholds.

What is the best way to validate hidden assumptions in an OpenSpec planning phase?

Validating hidden assumptions in OpenSpec proposals involves iteratively analyzing documents during the planning phase to generate structured findings on consistency and feasibility, then updating change ID files to resolve identified gaps.

Can I use multi-vendor review for OpenSpec proposal refinement?

Multi-vendor review is supported for OpenSpec proposal refinement by optionally dispatching parallel reviews and integrating consensus findings back into the proposal documents to ensure comprehensive quality validation.

Does iterate-on-plan work with a coordination layer for proposal updates?

The iterate-on-plan skill detects and leverages an available coordination layer for handoff, memory, and guardrails during OpenSpec proposal updates, ensuring iterative document changes follow established guardrails.

What are the limitations of automated quality analysis for OpenSpec changes?

Automated quality analysis for OpenSpec changes operates within severity thresholds to determine which proposal, tasks, design, and spec files get updated, meaning corrections below the threshold may not be automatically applied during the iterative refinement process.