oat-project-discover

Project discovery clarifies requirements and scope by gathering constraints through interactive dialogue, identifying gray areas, and proposing solution approaches with tradeoffs before development begins. It ensures a solid foundation by systematically exploring user needs and technical boundaries.

Documenting project decisions and boundaries involves recording gathered requirements, explored gray areas, and chosen approaches in a discovery.md file. This structured discovery output captures the project context and tradeoffs evaluated during the initiation phase.

Identifying project gray areas requires guided natural language dialogue that systematically questions user needs, technical constraints, and desired outcomes. This structured discovery process highlights undefined scope elements needing further definition and validation.

Yes, approach exploration proposes and validates different solution approaches alongside their tradeoffs during project discovery. It facilitates interactive dialogue to evaluate constraints and context, ensuring the chosen direction aligns with documented project boundaries.

Requirement gathering operates within the OAT framework, which manages project state and checks knowledge base staleness during discovery. No external dependencies are required to initiate the structured dialogue for clarifying project needs.

Structured project discovery is needed when kicking off a new software feature with unclear initial scope or undefined requirements. It systematically asks questions about user needs and technical constraints to establish a solid foundation before proceeding.