kiro-discovery

Project discovery determines the optimal action path for new projects by using structured dialogue to refine scope, deciding whether to update existing specs, create new ones, or proceed directly to implementation.

Structured dialogue is needed when refining new project ideas to clarify user intent, define project boundaries, and determine whether specs require updating, creation, or mixed decomposition.

Yes, you can create multiple specs in parallel for a single initiative. The process includes cross-spec review to catch contradictions and ensure consistency across the generated project documentation.

Automated documentation generates brief.md and roadmap.md files to capture project context and decisions, providing a clear record of the scope defined during the structured discovery dialogue.

Project discovery works without existing specs by evaluating the new idea and determining the optimal path, which may involve creating new specs, mixed decomposition, or proceeding with direct implementation if no spec is needed.

Spec decomposition is preferred over direct implementation for complex projects to ensure clarity, refine scope through structured dialogue, and generate documentation that guides multi-spec initiatives.