define-goal

To turn vague product intentions into measurable objectives, you define concrete goals with specific success criteria and scope boundaries before starting work. This process converts fuzzy requests into testable, quantitative outcomes.

Goal refinement in product management is the process of shaping and clarifying an existing objective to make it testable. It transforms an unclear request into a measurable objective with defined acceptance criteria to guide subsequent tasks.

Yes, you need a YAML frontmatter that includes the name and description to define success criteria for the goal tool. This format enforces a measurable objective, success criteria, and scope boundaries for product management workflows.

No, you cannot use this approach to manage long-running execution artifacts or decision logs. It is designed strictly for goal creation and refinement, not for managing durable snapshots or long-running execution artifacts.

You need to set scope boundaries for an objective when you are converting a vague user intent into a measurable goal. Defining scope boundaries ensures the objective remains testable and guides subsequent tool usage without expanding unmanageably.