kiro-discovery

Spec boundary discovery identifies whether to update an existing spec, create a new spec, or undergo mixed decomposition by performing lightweight metadata scans and steering checks. It routes decisions through a validated path framework to ensure safe, auditable progress before implementation.

Project idea decomposition uses structured dialogue to refine ideas and identify the safest scope for work. It applies context-aware discovery using steering docs and existing specs to minimize ambiguity and reduce scope drift.

The path determination framework routes new work items across paths A through E with staged validations. It requires explicit confirmation before creating or batching specs to enforce safe, auditable progress and minimize boundary drift.

Context-aware discovery heavily relies on existing steering docs and specs to reduce ambiguity during work scope clarification. Loading this context allows the process to perform accurate boundary decisions and determine the correct action path.

You should avoid using structured dialogue for boundary discovery when a work item clearly proceeds without a spec. If the task requires no spec, the path framework routes it accordingly, bypassing the need for decomposition or steering checks.

Yes, you can batch specs during the discovery process, but the framework requires explicit confirmation before creating or batching them. This validation step enforces safe, auditable progress and prevents uncontrolled scope drift.