intent-driven-development

Turns ambiguous or high-risk changes into scoped acceptance criteria with observable outcomes and appropriate verification methods.

When to use it

Use to clarify features, define acceptance criteria, de-risk sensitive changes, or prepare implementation handoffs; avoid trivial edits, active debugging, code review, and requests whose acceptance conditions are already clear.

Give it a proposed change; it returns an acceptance brief, asks for decisions on blockers, and continues implementation when requested and unblocked.