ship-it

Defining done criteria upfront prevents scope creep by requiring 3-5 binary, verifiable conditions that determine completion. Explicit non-goals and metadata documentation ensure measurable outcomes and clear boundaries before implementation begins.

A definition of done is a set of testable criteria that ensures deterministic handoffs by acting as a formal acceptance gate before execution. It requires explicit non-goals and binary criteria to prevent vague implementations during workflow planning.

Set non-goals and acceptance criteria by invoking the workflow command on a specific node ID to activate it. Define 3-5 binary done criteria, explicitly state non-goals to prevent mid-task drift, and record everything in node metadata for traceability.

Yes, you can use binary done criteria for quality assurance by defining 3-5 verifiable conditions that determine when work is complete. This formal acceptance gate ensures deterministic handoffs and prevents vague implementations in software engineering tasks.

You need to document metadata for task acceptance criteria when planning work on a tracked node in a weave workflow. Recording done criteria, non-goals, and acceptance criteria in node metadata provides traceability for audits and ensures deterministic handoffs.