discovery-skill

To turn an ambiguous project request into a measurable specification, define the outcome hypothesis, assign an explicit owner, and establish clear success criteria. This ensures the delivery request is approvable before planning begins.

Defining project scope and non-goals during intake requires separating in-scope work from explicit non-goals. You must also document assumptions and open questions to clarify responsibility before execution starts.

Yes, you need a validated project scaffold before planning delivery work. Creating or updating the scaffold and validating the resulting spec against runtime rules ensures the contract is actionable for execution.

Use outcome definition for early-stage project intake when scope, success criteria, or responsibility are not yet defined. It shapes a clear outcome hypothesis when the work needs approval before planning can proceed.

Scope clarification handles open questions and assumptions by explicitly separating in-scope work from non-goals. It produces an assumptions list and clarification questions to resolve fuzzy constraints before execution.

Yes, you can validate a project specification against delivery runtime rules. Operational setup validates the authored spec to ensure the resulting contract is actionable before the project moves into execution.