agentleFS
QuirkybrainQuirkybrain/claude-code-swe-framework/.claude/skills/clarification-gate/SKILL.md

clarification-gate

Skill1 starsChanged 53 days agoMITView on GitHub

Decide whether unresolved ambiguity, conflict, intent, or authority requires a user decision and formulate bounded options with tradeoffs. Use before making material product, architecture, technology, data, security, deployment, cost, or high-impact choices.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run when multiple reasonable interpretations exist, assets conflict, a choice has material downstream impact, or the actor lacks authority …

    line 14
  2. Distinctive:

    Search persisted Artifacts and State to ensure the question was not already answered.

    line 25
  3. Distinctive:

    Test whether existing context or a strong low-risk convention resolves it reliably.

    line 31
  4. Distinctive:

    If material, identify two or three viable, mutually distinguishable options.

    line 33
  5. Distinctive:

    Ask a concrete, structured question with limited options and allow the user to provide another answer.

    line 36
  6. Distinctive:

    After response, persist it in a Requirement, Constraint, Decision, or ADR and close the clarification.

    line 38
  7. Distinctive:

    Run Change Impact and recompute the Minimum Necessary Path when the answer changes prior assumptions or work.

    line 39
  8. Distinctive:

    Must ask for material product behavior, architecture, stack, data, security, deployment, cost, destructive action, or broad …

    line 43
  9. Distinctive:

    Do not ask again when a valid persisted answer applies.

    line 47
  10. Distinctive:

    No legitimate decision options can be formed from available evidence.

    line 58
  11. Distinctive:

    Stop when no material question exists and low-risk assumptions are recorded, or after issuing one bounded question and pausing affected …

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Clarification Gate

Purpose

Prevent invented user intent while avoiding unnecessary questions for low-risk choices that evidence or strong convention resolves safely.

Trigger

Run when multiple reasonable interpretations exist, assets conflict, a choice has material downstream impact, or the actor lacks authority to proceed.

Inputs

  • Exact ambiguity or decision, affected target, and blocked work.
  • Relevant Requirements, Constraints, decisions, assumptions, assets, and prior answers.
  • Reasonable options, consequences, reversibility, risk, cost, and downstream impact.
  • Execution Mode and decision owner.

Prerequisites

  • Search persisted Artifacts and State to ensure the question was not already answered.
  • Separate missing factual evidence from a genuine preference or authority decision.

Procedure

  1. State the unresolved issue and why it matters to the current target.
  2. Test whether existing context or a strong low-risk convention resolves it reliably.
  3. Evaluate impact on product behavior, architecture, technology stack, data model, security, deployment, cost, and large downstream work.
  4. If material, identify two or three viable, mutually distinguishable options.
  5. Explain each option's user-visible or engineering consequences concisely.
  6. Recommend an option only when evidence supports a recommendation; do not disguise it as an automatic decision.
  7. Ask a concrete, structured question with limited options and allow the user to provide another answer.
  8. Set the affected path to USER_DECISION_REQUIRED while leaving independent work available.
  9. After response, persist it in a Requirement, Constraint, Decision, or ADR and close the clarification.
  10. Run Change Impact and recompute the Minimum Necessary Path when the answer changes prior assumptions or work.

Decision Rules

  • Must ask for material product behavior, architecture, stack, data, security, deployment, cost, destructive action, or broad downstream-impact decisions.
  • May infer only low-risk, local, reversible choices supported by context or clear convention.
  • Record a consequential inference as an Assumption with rationale and confirmation path.
  • FULL_AUTO does not grant authority to invent material intent.
  • Do not ask again when a valid persisted answer applies.

Outputs

  • Gate verdict: PASS, USER_DECISION_REQUIRED, or BLOCKED.
  • Structured question, options, tradeoffs, recommendation if justified, and affected scope.
  • Persisted answer/assumption and closed clarification after resolution.
  • Change-impact and path-recomputation trigger when applicable.

Failure Cases

  • No legitimate decision options can be formed from available evidence.
  • The decision owner is unavailable.
  • Options conceal a prerequisite fact or use misleading tradeoffs.
  • Conflicting persisted decisions have unclear authority.

Escalation

Request additional analysis before questioning when options are technically undefined. Escalate authority conflicts explicitly. Never choose silently to keep the workflow moving.

Stop Conditions

Stop when no material question exists and low-risk assumptions are recorded, or after issuing one bounded question and pausing affected work. Resume only after the answer is persisted.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.