clarify

Resolves ambiguities in a single DAE artifact through an iterative interview.

150|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/swingerman/engineer --skill clarify-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/swingerman/engineer/tree/main/engineer/skills/clarify
Command: npx skills add https://github.com/swingerman/engineer --skill clarify-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve ambiguities in a specification document?▼

Run /engineer.clarify with the feature slug and artifact name, or a direct file path. The skill identifies ambiguous lines one at a time, asks a targeted question for each, and edits the resolution into the artifact after your confirmation.

What files can the clarify skill process?▼

It works on one DAE artifact at a time: feature.md, acs.md, spec.md, plan.md, or CHARTER.md. It also loads the parent contract (feature.md or CHARTER.md) for grounding but only edits the target artifact.

Can clarify fix contradictions between multiple spec files?▼

No. Cross-artifact contradictions are out of scope and handled by the consistency-check skill. Clarify only resolves ambiguities within a single artifact and flags downstream files that may need updates via feature-edit.

When should I use clarify versus feature-edit?▼

Use clarify to tighten vague wording inside one artifact without changing what the feature does. Use feature-edit when a resolution must cascade across multiple files or when you are changing the feature's actual behavior.

What happens if clarify finds no ambiguities?▼

The skill reports that no ambiguities were found and stops without making edits. It does not modify the artifact or emit downstream staleness flags in that case.