Clarify a Task or Decision

VerifiedSafe

Helps clarify a task or decision through guided, interactive questioning. Uses a mix of open-ended context questions and structured AskUserQuestion prompts to gather preferences, scope, and priorities. Best when requirements are unclear or multiple approaches need comparison.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#task-clarification#decision-making#guided-questioning#requirements-gathering#scope-definition

Recommended for

Automated summary

Helps the user clarify a task or decision through guided, interactive questioning.

Strengths

  • Reduces ambiguity in requirements
  • Structures thinking with predefined and adaptive questions
  • Batches related questions to minimize back-and-forth

Limitations

  • Requires human interaction for open-ended answers
  • May feel too rigid if user already has a clear vision
  • Depends on quality of options provided by the tool
When to use it

Use this skill when you need to nail down preferences, scope, or priorities for a complex task.

When not to use it

Avoid it if the task is already well-defined or a simple direct question would suffice.

Security analysis

Safe
Quality score92/100

The skill is purely a conversational guidance tool; it does not instruct execution of any system commands, network operations, or file deletions. It only suggests writing to a designated memory bank file within the user's project, which poses no security risk.

No concerns found

How this analysis is made

Examples

Clarify approach for a new feature
I need to clarify the approach for implementing user authentication. Use the clarify skill.
Define scope for a refactoring task
Clarify the scope of refactoring the payment module – should it include edge cases and testing?
Prioritize project goals
Help me clarify priorities for the upcoming sprint: speed vs quality vs flexibility.

name: clarify description: Clarify a task or decision through guided questioning

Clarify: $ARGUMENTS

Help the user clarify a task or decision through guided, interactive questioning.

Instructions

  1. Initial Context: Ask 1-2 open conversational questions to understand the broad context (AskUserQuestion doesn't fit here - need free-form)

  2. Structured Clarification: Once context is established, use the AskUserQuestion tool to efficiently gather:

    • Preferences between approaches
    • Scope boundaries
    • Priority trade-offs
    • Constraint selections
  3. Batch Related Questions: Group related questions (up to 4) in a single AskUserQuestion call to reduce back-and-forth

  4. Follow-up Freely: If user selects "Other", follow up conversationally

  5. Summary: Provide structured summary of decisions

When to Use AskUserQuestion

USE the tool when:

  • Presenting 2-4 clear, distinct options
  • Asking about preferences, priorities, or scope
  • Options have meaningful trade-offs to describe
  • Questions are independent enough to batch

DON'T use the tool when:

  • Gathering open-ended context ("What's the goal?")
  • Deep exploration where options aren't yet clear
  • Single yes/no that's faster to ask directly

Example Flow

Phase 1: Context (Conversational)

"What aspect of [topic] needs clarification?" Wait for response

Phase 2: Structured Choices (AskUserQuestion)

Use the AskUserQuestion tool with questions like:

questions:
  - question: "Which approach do you prefer for X?"
    header: "Approach"
    options:
      - label: "Option A (Recommended)"
        description: "Faster, less flexible"
      - label: "Option B"
        description: "More complex, more control"
    multiSelect: false

  - question: "What should be in scope?"
    header: "Scope"
    options:
      - label: "Core feature only"
        description: "Minimal implementation"
      - label: "With edge cases"
        description: "Production-ready"
      - label: "Full solution"
        description: "Including tests, docs"
    multiSelect: false

Phase 3: Summary

Provide structured output (see Output Format below)

Question Templates for AskUserQuestion

Priority Trade-offs

question: "What's more important for this task?"
header: "Priority"
options:
  - label: "Speed"
    description: "Get it working quickly, refine later"
  - label: "Quality"
    description: "Take time to do it right"
  - label: "Flexibility"
    description: "Easy to change/extend later"
multiSelect: false

Scope Definition

question: "What scope makes sense?"
header: "Scope"
options:
  - label: "Minimal"
    description: "Just the core requirement"
  - label: "Standard"
    description: "Core + common edge cases"
  - label: "Comprehensive"
    description: "Full solution with tests"
multiSelect: false

Approach Selection

question: "Which approach should we take?"
header: "Approach"
options:
  - label: "[Approach A] (Recommended)"
    description: "[Why A is good]"
  - label: "[Approach B]"
    description: "[Why B is good]"
multiSelect: false

Constraint Selection

question: "Which constraints apply?"
header: "Constraints"
options:
  - label: "Backward compatible"
    description: "Must not break existing behavior"
  - label: "Performance critical"
    description: "Speed/memory constraints apply"
  - label: "Minimal dependencies"
    description: "Avoid adding new libraries"
multiSelect: true

Output Format

After clarification is complete, provide:

## Clarification Summary

**Topic**: [What was clarified]

**Key Points**:
- Point 1
- Point 2
- Point 3

**Decisions Made** (if applicable):
- Decision 1
- Decision 2

**Next Steps**:
- Action 1
- Action 2

Decision Persistence

When to Persist

Always persist when ALL of these conditions are met:

  1. Memory bank exists (.claude/memorybank/ directory found)
  2. Decisions were made during clarification (not just information gathering)
  3. Decisions affect project direction, approach, or scope

What to Persist

Record to .claude/memorybank/progress.md:

### Clarification: [Topic] ([Date])

**Decisions Made**:
| Decision | Rationale | Impact |
|----------|-----------|--------|
| [Decision 1] | [Why this was chosen] | [What areas affected] |
| [Decision 2] | [Why this was chosen] | [What areas affected] |

**Context**: [Brief context from clarification]

Process

  1. After clarification summary is presented, check if memory bank exists
  2. If memory bank exists and decisions were made:
    • Get current timestamp
    • Append decision entry to progress.md
    • Update session.md if focus changed
    • Inform user: "Decisions recorded to memory bank"
  3. If no memory bank: Show warning from Error Handling section

Optional: Update session.md

If clarification changed the current focus or approach:

## Focus Area
[Updated focus based on clarification]

## Recent Work ([date])

### Clarification Completed
- Clarified: [topic]
- Key decisions: [brief list]

User Notification

After persisting:

## Decisions Recorded

Clarification decisions have been saved to:
- progress.md: Decision log with rationale
[- session.md: Updated focus area (if changed)]

Ready to proceed. [Skill chaining suggestion]

Skill Chaining

After clarification is complete, suggest appropriate next actions:

| Situation | Suggestion | |-----------|------------| | Clarified approach/plan | "Run /plan to create implementation plan with these decisions" | | Clarified requirements | "Run /document to record these decisions in progress.md" | | Resolved blocker | "Continue with work. Run /logwork add to log progress" | | Clarified scope | "Ready to proceed. Start with: [first step based on decisions]" | | Significant decisions made | "Run /document first to persist decisions, then /plan to create detailed plan" | | Clarified but still uncertain | "Consider /clarify [different aspect] for remaining ambiguity" |


Error Handling

No Memory Bank

If .claude/memorybank/ doesn't exist when trying to record decisions:

## Note: Memory Bank Not Found

Clarification complete. However, memory bank not found at `.claude/memorybank/`.

To persist these decisions for future sessions, run `/onboard-claude` to initialize the memory bank, then run `/document` to record the decisions made during clarification.

Important: Clarify can still run without memory bank (for ad-hoc clarification), but should warn if decisions can't be persisted

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/clarify-a-task-or-decision-mmio71gr/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/clarify-a-task-or-decision-mmio71gr' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/clarify-a-task-or-decision-mmio71gr/download' --output '.skill-downloads/clarify-a-task-or-decision-mmio71gr/SKILL.md.part' && mv '.skill-downloads/clarify-a-task-or-decision-mmio71gr/SKILL.md.part' '.skill-downloads/clarify-a-task-or-decision-mmio71gr/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/clarify-a-task-or-decision-mmio71gr/SKILL.md' && test -s '.skill-downloads/clarify-a-task-or-decision-mmio71gr/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/clarify' && cp -R '.skill-downloads/clarify-a-task-or-decision-mmio71gr' '.claude/skills/clarify'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/clarify-a-task-or-decision-mmio71gr'

openskills read 'clarify-a-task-or-decision-mmio71gr'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/clarify-a-task-or-decision-mmio71gr/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills