What problem does it solve? Specification documents often contain vague language, undefined terms, or unclear scope boundaries that cause downstream implementation errors. This Skill systematically finds and resolves those ambiguities in one artifact at a time before they propagate. ## Core Features & Use Cases - Ambiguity Detection: Scans a single DAE artifact (feature.md, acs.md, spec.md, plan.md, or CHARTER.md) for language interpretable two ways, underspecified requirements, undefined domain terms, and internal contradictions. - Iterative Interview: Resolves each ambiguity one at a time by quoting the ambiguous line and asking a targeted multiple-choice or open-ended question. - In-Place Editing with Staleness Flags: Encodes each resolution directly into the target artifact with old-to-new confirmation, then flags downstream artifacts that may need propagation via feature-edit. - Use Case: After drafting a spec.md, run /engineer.clarify to tighten vague acceptance criteria before handing the spec to planning. ## Quick Start Ask the agent to clarify the ambiguities in your feature spec by running /engineer.clarify with the feature slug and artifact name.