clarify is agent-read markdown (skill) from swingerman/engineer: Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec", "resolve ambiguities", "this is vague — tighten it"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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).
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
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 agent 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/next/SKILL.md · Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project…
swingerman/engineer · engineer/skills/onboard/SKILL.md · Use to bring a project into the DAE methodology, or to check an onboarded project for gaps. Triggers —…
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…
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…
saadshahd/moo.md · hope/skills/clarify/SKILL.md · Turn words with two readings into one confirmed ask. Use when the user's words admit two readings that would build…
toongri/oh-my-toong-playground · skills/clarify/SKILL.md · MANDATORY before any implementation when request is vague or has multiple interpretations. Triggers on "clarify"…
qwerfunch/cladding · plugins/antigravity/skills/clarify/SKILL.md · Advance Cladding onboarding after the user answers a pending product question. Use the MCP prepare/apply flow, preserve…
