agentleFS
mag123cmag123c/toktrack/.claude/skills/clarify/SKILL.md

clarify

Skill196 starsChanged 13 days agoMITView on GitHub

Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.

83 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quieter, arrange and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    quieter

    Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

    Also in 29 projects that use this

  • HK-hubSkill

    arrange

    Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

    Also in 14 projects that use this

  • zwy123zwySkill

    normalize

    将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。

    Also in 19 projects that use this

  • owshq-mecSkill

    layout

    Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

    Also in 8 projects that use this

  • +8 more from HK-hub

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Remove ambiguity via quick Q&A, generate minimal specs, and present the PLAN inline.

    line 76
  2. Distinctive:

    Escalation Check: Check escalation conditions (see below)

    line 82
  3. Very specific:

    Create DRAFT: Write .dev/specs/{name}/DRAFT.md (minimal version — What, Why, Scope, Success Criteria)

    line 83
  4. Very specific:

    Summary + Create PLAN: Before/After comparison → Write .dev/specs/{name}/PLAN.md

    line 84
  5. Distinctive:

    No assumptions → Ask questions

    line 88
  6. Very specific:

    After presenting the PLAN inline, call /implement immediately.

    line 156

“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “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

/clarify — Adaptive Requirements Clarification

Chain (MUST)

PreviousCurrentNext
Session start/clarifyPresent PLAN inline → /implement

Core Model

/clarify → Measure complexity → Clear enough?
                                ├─ Yes → Present PLAN inline → /implement
                                └─ No  → Deeper clarify (explore, analyze, DRAFT...)
                                         → Re-measure → Repeat

Exit condition: "Is this enough info to implement?" — Critical Unknown=0 + remaining items are made visible (Provenance).


Reference Files (load as needed — chaining)

WhenFile
Tagging provenance on key decisions/assumptions / probe decisionsreferences/provenance.md
Pre-PLAN user confirmationreferences/checkpoint.md
When document authority/reading order is unclearreferences/doc-roles.md
Full Deep path proceduredeep/DEEP.md
PLAN/DRAFT structure (Lite/Full + Clarify Verdict)templates/

Inline essentials only: probe-don't-tag (if cheaply verifiable, measure instead of tagging), PLAN=intent · WRAP/DECISIONS=fact, do not hide inferences. Details in the references above.


Step 0: Route — Complexity Assessment

Measure complexity internally upon receiving request (do not expose to user).

Complexity Signals

SignalLOWHIGH
Request lengthShort and specificLong or ambiguous
Keywords"add", "fix", "change""design", "migration", "from scratch"
UncertaintyNone"not sure", "how should I"
Impact scopeSingle file/moduleCross-cutting, multiple services
RiskLow (UI, text)High (DB, auth, breaking API)
Existing patternsClearly existNone or unfamiliar stack
  • LOW → Shallow Path (completed within this file)
  • HIGH → Deep Path (see deep/DEEP.md)
  • Ambiguous → Start Shallow, monitor escalation conditions

Shallow Path (Low Complexity)

Remove ambiguity via quick Q&A, generate minimal specs, and present the PLAN inline.

Execution

  1. Record: Log original request + identify ambiguous parts
  2. Question: AskUserQuestion (specific options, 2-3 rounds)
  3. Escalation Check: Check escalation conditions (see below)
  4. Create DRAFT: Write .dev/specs/{name}/DRAFT.md (minimal version — What, Why, Scope, Success Criteria)
  5. Summary + Create PLAN: Before/After comparison → Write .dev/specs/{name}/PLAN.md
  6. Present PLAN: Present the PLAN inline in the conversation (do NOT enter plan mode), then immediately call /implement. The plan file must be written to .dev/specs/{name}/PLAN.md

Rules

  • No assumptions → Ask questions
  • Clarify to TDD-ready level
  • Target resolution within 3 rounds

Escalation → Deep Path

Switch to Deep Path if any of these are detected:

  • Scope still undefined after 3 rounds of questions
  • New uncertainties keep emerging from user answers
  • Impact scope expanded beyond initial estimate (single → multi-module)
  • Risk indicators found (DB schema, auth, breaking changes)
  • User doesn't know the approach itself ("I don't know how to do this")

On switch: Inform "Scope is more complex than expected. Exploring the codebase first." then follow the process in deep/DEEP.md.


Deep Path

When complexity is HIGH or escalated from Shallow.

See deep/DEEP.md for the full process.

Summary:

  1. Classify intent (7 types) → Determine strategy
  2. 3 parallel exploration agents → Understand codebase
  3. Generate DRAFT → Interview → Continuously update
  4. On user explicit request → Analysis agents → Generate PLAN → Reviewer loop
  5. Present PLAN inline → immediately call /implement (no plan mode entry)

DECISIONS.md Recording (MUST)

Record decisions in .dev/DECISIONS.md before finalizing plan:

SituationRequired Record
New feature designDecision background, alternatives, reasoning
Architecture choiceConsidered options, selection rationale
Trade-offsWhat was sacrificed and what was gained
## YYYY-MM-DD: {feature-name}
- **Decision**: What was decided
- **Reason**: Why this choice was made
- **Alternatives**: Options considered but not chosen
- **Reference**: .dev/specs/{feature-name}/PLAN.md (if exists)

Plan File Requirements

Plan files must include:

  • Specify implementation via /implement skill
  • Verification method (test execution)
  • Confirmation that .dev/DECISIONS.md recording is complete

Plan File Location: The PLAN must be written to .dev/specs/{name}/PLAN.md.

Important: Plans that do not use /implement will not be approved.


NEXT STEP (Auto-execute)

After presenting the PLAN inline, call /implement immediately. Do NOT enter plan mode; do not ask "Should I implement?".

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.