Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec", "resolve ambiguities", "this is vague — tighten it".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# clarify
Resolve ambiguities in **one** DAE artifact through an iterative interview. A cross-cutting quality gate — runs on any artifact at any pipeline stage.
The clarify *pattern* is also embedded inside artifact-producing skills for their own in-flight ambiguities; this standalone skill is for ad-hoc cleanup after the fact.
## When to use
On any one of: `feature.md`, `acs.md`, `spec.md`, `plan.md`, `CHARTER.md`. Invoked as `/engineer.clarify <slug> <artifact>` or `/engineer.clarify <path>`.
**Not for:** cross-artifact contradictions (`consistency-check`); changing what a feature does (`feature-edit`); resolutions that cascade across files (clarify the source here, then `feature-edit`).
## Workflow
1. **Resolve + load** — resolve the methodology root + manifest via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py` (see `references/resolving.md`); locate the target artifact. Also load its parent contract for grounding (`feature.md` for acs/spec/plan; `CHARTER.md` for feature.md).
…
The line at the top of this page pins the label git:20260516.48406db, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_veisg5cai4fuw37j
GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/clarify
GET https://markdownregistry.com/api/v1/blob/86473e72c00a405cf1bdc32688a0f91c99d562a3d2c3341b39cb663185199e84
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
swingerman/engineer · crap-analyzer/skills/crap-analyzer/SKILL.md · Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP…
swingerman/engineer · engineer/skills/arch-check/SKILL.md · Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden…
swingerman/engineer · engineer/skills/atdd/SKILL.md · Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. The…
swingerman/engineer · engineer/skills/consistency-check/SKILL.md · Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers —…
swingerman/engineer · engineer/skills/discover-acs/SKILL.md · Use when a Ready feature needs its acceptance criteria discovered before specs are written. Triggers —…
swingerman/engineer · engineer/skills/discuss/SKILL.md · Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss"…
swingerman/engineer · engineer/skills/express/SKILL.md · Use to build an XS (express-lane) feature in one pass — intake→implement→verify in a single context, no handoff chain…
swingerman/engineer · engineer/skills/feature-edit/SKILL.md · Use when an in-flight feature must change — scope shifts, an AC is refined, the plan evolves, a behavior is added or…
swingerman/engineer · engineer/skills/feature-init/SKILL.md · Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers —…
swingerman/engineer · engineer/skills/fix/SKILL.md · Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers —…
swingerman/engineer · engineer/skills/harden/SKILL.md · Use after a feature passes Light Verify (CP7), to prove the tests actually catch bugs and, where the code warrants it…
swingerman/engineer · engineer/skills/lean/SKILL.md · Use to formally verify real code with Lean 4. Model a function or state machine as written, prove an invariant for…
fengshao1227/ccg-workflow · templates/skills/impeccable/clarify/SKILL.md · Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand…
zaxbyhub/opencode-swarm · .opencode/skills/clarify/SKILL.md · Full execution protocol for MODE: CLARIFY -- structured clarification funnel with critic review before surfacing user…
zaxbyhub/opencode-swarm · .claude/skills/clarify/SKILL.md · Full execution protocol for MODE: CLARIFY -- structured clarification funnel with critic review before surfacing user…
ericrisco/rsc-harness · skills/clarify/SKILL.md · Use when a spec exists and must be de-risked before planning — run the gap checklist over its four ASDD questions and…
umputun/cc-thingz · plugins/workflow/skills/clarify/SKILL.md · This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and…
educlopez/ui-craft · .gemini/skills/clarify/SKILL.md · UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request…
educlopez/ui-craft · .codex/skills/clarify/SKILL.md · UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request…
educlopez/ui-craft · .agents/skills/clarify/SKILL.md · UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request…
