Results for “requirements-clarification”

Clarify requirements before implementing by asking targeted questions when a request has multiple plausible interpretations or key details are unclear.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

Use only when the request concerns standards, responsibility, complexity, smells, naming, refactoring catalogs, or task-plan rules; not routine work.

Create detailed phase plan (PLAN.md) with verification loop