iterative-evolver

Run a full iterative evolution cycle — Assess, Analyze, Plan, Execute, and Reflect. Auto-detects domain or prompts for it. Use for any subject that needs iterative improvement against goals.

Run only the Analyze phase — research the external landscape for competitors, trends, opportunities, and threats. Requires an existing assessment or goals.

Run only the Assess phase — evaluate current state against goals. Produces a structured assessment without creating plans or making changes.

Run only the Execute phase — carry out a previously created improvement plan. For software domain evolutions, delegates to kbd-process-orchestrator as the inner loop for fine-grained task execution with OpenSpec detection and artifact-refiner QA. Requires an existing plan.json.

Run only the Plan phase — create a prioritized improvement plan. Requires an existing assessment and optionally an analysis.

Generate an evolution report from current state data. Produces a human-readable markdown report summarizing the full evolution cycle. Aggregates KBD phase results and artifact-refiner QA metrics when available. Optionally refines the report through artifact-refiner content refinement.

Check the current status of an evolution cycle. Shows iteration count, goal alignment, phase completion, and convergence status.

Domain-agnostic PMPO improvement loop: Assess -> Analyze -> Plan -> Execute -> Reflect over any subject (software, product, business, research, operations). Use when the user wants to improve or evolve something over repeated passes, asks "make this better", "iterate on this", "evolve this", or when a target needs assessing before changes are planned. Do NOT use for a single scoped code change (just make it), for standing always-on automation with termination criteria (see pmpo-outer-loop), or for gathering a missing fact mid-stage (see pmpo-elicit).