clarify

You can resolve ambiguous requirements in a single specification document by running an iterative interview loop that asks one focused question per ambiguity and applies in-place edits to eliminate uncertainty without cascading changes across other artifacts.

Fixing undefined domain terms in feature or spec markdown files involves identifying interpretable lines, grounding them with the parent contract, and asking targeted questions to turn vague requirements into explicit decisions encoded directly in the document.

Yes, you can clarify contradictions in acceptance criteria without altering other project artifacts by performing single-artifact ambiguity resolution, which isolates edits to the target file and flags downstream staleness for separate handling.

To handle unclear scope boundaries in a DAE methodology plan.md file, load the methodology root and manifest, ground the content with the relevant parent contract, and resolve the boundary ambiguity through bounded multiple-choice or open-ended questions.

No, the clarification process does not edit multiple files simultaneously; it resolves internal contradictions in a single artifact in-place, avoids cross-artifact contradiction handling, and recommends the appropriate next skill to propagate any necessary downstream changes.

Resolving a vague requirement in CHARTER.md flags downstream staleness instead of updating all related files to prevent cascading edits, ensuring traceability by isolating changes to one artifact and recommending the correct next skill for propagation.