goal-grill

To clarify undefined goals and acceptance criteria, you can use a 3-layer goal tightening workflow that elicits Vision, Outcome, and Eval metrics through one-question-at-a-time progression before any code is written. This ensures measurable outcomes are defined upfront.

Defining vision and outcome metrics without a PRD involves applying a prd-lite session workflow that asks only the minimum questions needed to establish what you are trying to achieve and how you will judge success, drafting a preview for approval before final writeout.

Yes, you can resume a goal clarification session using session-aware NEW, RESUME, and REVIEW handling, allowing you to continue from a saved session or refine an existing goal document without losing your previous progress.

The goal elicitation process supports optional web escalation rules that request web checks specifically when needed to fill in uncertain, time-sensitive, or spec-driven parts of the goal during the clarification workflow.

To generate and save goal documentation, the workflow drafts a preview and waits for your explicit approval at a writeout gate before writing the finalized vision, outcome, and acceptance criteria to docs/output/goals/<slug>.md.

You need to define acceptance criteria for non-trivial repo tasks whenever starting work without existing goal documentation or a PRD-equivalent artifact, ensuring the vision, outcome metrics, and eval layers are established before implementation begins.