task-clarification-harness

Use a repository-grounded pre-implementation clarification harness to restate ambiguous tasks, inspect available repository evidence, and separate confirmed facts from inferences before writing any code.

Defining scope boundaries for a cross-cutting refactor requires structured impact mapping to identify impacted areas, enumerate risks and invariants, and generate a validation-ready implementation contract with acceptance criteria.

To create an implementation contract for production-readiness work, restate the task, inspect repository evidence, enumerate ambiguities, and output a readiness decision alongside a concrete validation plan.

Yes, a human-in-the-loop validation plan is ideal for auth-sensitive changes because it forces an evidence-based pass to surface unknowns, define invariants, and set scope constraints before implementation begins.

You need a repository-grounded clarification artifact for multi-area bug fixes when tasks are broad, underspecified, or likely to drift without explicit boundaries and validation criteria to keep changes targeted.

Yes, a pre-implementation clarification harness works for high-drift feature additions by requiring a readiness decision that blocks coding until key decisions, risks, and scope boundaries are explicitly defined.