swingerman/clarify
engineer/skills/clarify/SKILL.md
Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec", "resolve ambiguities", "this is vague — tighten it".
$ install --global
skillsauthnpx skillsauth add swingerman/atdd clarifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 17, 2026, 4:25 AM135.2s1 file scanned
SKILL.md
- name:
- clarify
- description:
- Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec", "resolve ambiguities", "this is vague — tighten it".
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
- Resolve + load — resolve the methodology root + manifest via
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md); locate the target artifact. Also load its parent contract for grounding (feature.mdfor acs/spec/plan;CHARTER.mdfor feature.md). - Identify ambiguities — within this one artifact: language interpretable two ways, underspecified requirements, undefined domain terms, unclear scope boundaries, internal contradictions. Cross-artifact contradictions are out of scope (→
consistency-check). If none found, say so and stop. - Resolve one at a time — per ambiguity, quote the ambiguous line and ask one question — multiple-choice (AskUserQuestion) when bounded, open-ended otherwise. Iterate until resolved or the user stops.
- Edit in place — encode each resolution into the target artifact; show old→new, confirm before writing. Edit only the target artifact.
- Flag downstream staleness — do NOT cascade. Identify downstream artifacts a resolution may have invalidated; list them in the handoff; recommend
feature-edit(which owns cascade). - Handoff — emit a summary.
Handoff
Emit per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null. If downstream staleness flagged: human_action_needed: yes, recommended_next: "/engineer.feature-edit to propagate".
References
- Foundation Design — artifact schemas
- The DAE methodology page — clarify as embedded pattern + standalone skill
Related Skills
swingerman/post-merge
data-ai
VerifiedTrustedCommunity
Use immediately after a PR is merged to clean up the local feature branch and resync main. Triggers — "/engineer.post-merge", "did we merge", "did we push", "PR merged", "post-merge cleanup", or right after a `gh pr merge` succeeds in the same session.
103SKILL.mdUpdated Jun 5, 2026
swingerman/fix
data-ai
VerifiedTrustedCommunity
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".
103SKILL.mdUpdated May 26, 2026
swingerman/reorient
testing
VerifiedTrustedCommunity
Use mid-task when the working thread is lost — after a context compaction, a long agent run, or coming back to a feature unsure of the role, the current checkpoint, or the next action. Triggers — "/engineer.reorient", "reorient", "re-anchor", "what should I be doing right now", "I lost track", "where was I".
103SKILL.mdUpdated May 20, 2026
swingerman/arch-check
development
VerifiedTrustedCommunity
Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden patterns, file naming, file size. Triggers — "/engineer.arch-check", "architecture check", "check architecture fitness", "does this follow the charter", "check layering".
103SKILL.mdUpdated May 19, 2026