product-iteration

You orchestrate data-driven product iterations by collecting signals, evaluating decisions, defining scope, and decomposing tasks. This structured workflow updates docs/prd.md and docs/iterations to maintain traceable, auditable decision history.

Traceability for product iteration decisions is maintained through documentation-driven execution that updates docs/iterations and docs/tasks. Consistency gates, dependency mapping, and change-guard compliance ensure an auditable, drift-free history.

Scope decomposition prevents drift by applying governance guardrails like consistency checks, dependency mapping, and change-guard compliant task breakdown. This ensures alignment with product-builder outputs while updating docs/tasks during iteration execution.

Yes, the workflow supports teams using existing docs/prd.md and iteration history stored in docs/iterations. It requires structured frontmatter in SKILL.md and applies consistency gates to align new decisions with your current documentation.

Initiate an iteration by collecting signals and drafting a prioritized decision plan. The workflow then moves through scope definition and task decomposition, automatically updating docs/iterations and docs/tasks to execute the iteration systematically.

Guardrails applied during scope decomposition include consistency checks, dependency mapping, and change-guard compliant task breakdown. These governance mechanisms align outputs with docs/prd.md to prevent undocumented changes and misaligned priorities.