Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
"/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변…
Install Clarify
$ npx skills add team-attention/hoyeon --skill clarify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install team-attention/hoyeon clarify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/clarify .claude/skills/clarify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "clarify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/clarify into .claude/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/team-attention/hoyeon/tree/main/skills/clarifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add team-attention/hoyeon --skill clarify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install team-attention/hoyeon clarify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/clarify .agents/skills/clarify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clarify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/clarify into .agents/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add team-attention/hoyeon --skill clarify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install team-attention/hoyeon clarify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/clarify .cursor/skills/clarify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clarify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/clarify into .cursor/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/team-attention/hoyeon.git --path skills/clarify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add team-attention/hoyeon --skill clarify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install team-attention/hoyeon clarify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/clarify .gemini/skills/clarify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clarify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/clarify into .gemini/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install team-attention/hoyeon clarifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add team-attention/hoyeon --skill clarify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/clarify .github/skills/clarify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clarify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/clarify into .github/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add team-attention/hoyeon --skill clarify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install team-attention/hoyeon clarify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/clarify .opencode/skills/clarify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clarify" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/clarify into .opencode/skills/clarify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clarify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
clarify- GitHub stars
- 173
- Token cost
- ~1.9k tokens
- SKILL.md length
- 797 words
- Files
- 3
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
"/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변…
- Works in 8 steps: Mirror — State the current understanding… → Map ambiguity branches — List the active… → Ask one question — Ask exactly one… → …
- Tasks that involve Requirements gathering
- SKILL.md covers Runtime Surface, Artifacts, Modes and Core Loop, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clarify is an agent skill from team-attention/hoyeon. "/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변 기록", "요구사항 명확화", "설계 명확화". Relentless ambiguity-resolution interview that records Q&A under .hoyeon/clarify/<topic/ and hands off to specify/blueprint/docs when clear.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `templates/clarity-summary.md` and `templates/qa-log.md`).
It sits in Agent Workflows, covering Requirements gathering. The repository describes itself as: Requirements-first Harness — derive, verify, execute. The licence is MIT.
When your agent uses it
- Tasks that involve Requirements gathering
Example prompts
- “/clarify”
- “clarify this”
- “keep asking until clear”
- “/clarify”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, Task, Write, Edit, AskUserQuestion
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Mirror — State the current understanding in 2-4 bullets.
- Map ambiguity branches — List the active ambiguity branches in memory
- Ask one question — Ask exactly one question. Include
- Explore instead of asking — If the answer is discoverable from the
- Record immediately — Append to qa-log.md after every exchange.
- Classify — Mark the branch as resolved, ambiguous, assumption, or
- Audit — After 3-5 Q&A turns, after each major branch, and before
- Continue or summarize — If auditor returns CONTINUE, ask the next
What it can do on your machine
Read from SKILL.md and the folder at commit 7cff032. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGrepGlobTaskWriteEditAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Clarify loads about 1.9k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 797 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Grep, Glob, Task, Write, Edit, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 797 words, ~1,944 tokens.
Download SKILL.mdSave it as
.claude/skills/clarify/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- clarify
- description
- "/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변 기록", "요구사항 명확화", "설계 명확화". Relentless ambiguity-resolution interview that records Q&A under .hoyeon/clarify/<topic>/ and hands off to specify/blueprint/docs when clear.
- allowed-tools
- Bash, Read, Grep, Glob, Task, Write, Edit, AskUserQuestion
- validate_prompt
- Must ask one question at a time, provide a recommended answer, record Q&A, and continue until the auditor finds no material ambiguity or the user stops. Must…
/clarify — Ambiguity Resolution Interview
clarify is a pre-spec interview loop. It is closer to grill-me than
specify: ask one precise question at a time, recommend an answer, record the
answer, and keep going until material ambiguity is gone.
Do not implement, plan execution, or generate final requirements. The output is traceable context for the next workflow.
Runtime Surface
Claude Code
- Use
AskUserQuestionfor mode selection and branching decisions. - Use
Task(subagent_type="clarity-auditor")at audit boundaries. - Use
Task(subagent_type="code-explorer")when a question can be answered from the codebase instead of asking the user.
Codex
- Use Codex-native structured input when available; otherwise ask one concise plain-text question at a time.
- Use
hoyeon-clarity-auditorwhen native adapters are loaded. - Use
hoyeon-code-explorerwhen codebase exploration can answer the question. - If native adapters are unavailable, perform the smallest direct read-only
pass and record that fallback in
qa-log.md.
Artifacts
Create a topic directory:
.hoyeon/clarify/<topic-slug>/
├── qa-log.md
└── clarity-summary.mdRead templates when writing artifacts:
templates/qa-log.mdtemplates/clarity-summary.md
Use a short kebab-case topic slug. If the current repo already has a Hoyeon
spec directory for the same work, mention it in frontmatter as related_spec.
Modes
Infer the mode from the user's request. If uncertain, ask first.
| Mode | Use For | Main Question Lens | Clear Enough When |
|---|---|---|---|
requirements | Product/feature intent before /specify | users, goal, non-goals, success, scope, flows, edge cases, constraints | $hoyeon-specify --context clarity-summary.md can start without guessing |
design | Architecture or implementation direction before planning | alternatives, boundaries, interfaces, data flow, trade-offs, risks, reversibility, verification | chosen direction, rejected alternatives, risks, and validation are explicit |
domain | Terms, concepts, and domain model | canonical terms, definitions, relationships, edge cases, conflicts with docs/code | key terms have stable definitions and unresolved terms are listed |
plan | Work sequencing before blueprint/execution | dependencies, acceptance criteria, blocking decisions, validation, rollback, ownership | no blocking execution decision remains |
Frontmatter fields:
mode: requirements | design | domain | plan
status: active | complete | paused
target_handoff: hoyeon-specify | hoyeon-blueprint | docs | noneDefault mode is requirements.
Core Loop
- Mirror — State the current understanding in 2-4 bullets.
- Map ambiguity branches — List the active ambiguity branches in memory: vague terms, hidden assumptions, unresolved forks, missing criteria, external facts/code facts to verify.
- Ask one question — Ask exactly one question. Include:
- why this question matters
- your recommended answer
- the trade-off behind the recommendation
- Explore instead of asking — If the answer is discoverable from the codebase or existing docs, explore first and ask only if evidence conflicts.
- Record immediately — Append to
qa-log.mdafter every exchange. - Classify — Mark the branch as
resolved,ambiguous,assumption, ordeferred. - Audit — After 3-5 Q&A turns, after each major branch, and before
summary, call the clarity auditor with the full
qa-log.md. - Continue or summarize — If auditor returns
CONTINUE, ask the next suggested question. IfSUFFICIENT, writeclarity-summary.md.
Question Rules
- Ask one question at a time.
- Always provide a recommended answer unless the question is purely factual and must be discovered.
- Prefer concrete options over open-ended prompts, but allow "Other".
- Do not ask the user for facts that code/docs can answer.
- Do not repeat a question. If the user does not know, choose a tentative
default, mark it
assumptionordeferred, and move on. - Keep pressure on vague words: "fast", "simple", "good", "production-ready", "secure", "later", "nice UX", "admin", "sync", "done".
Show full SKILL.md (285 more words)Show less
Mode-Specific Checks
requirements
Required branches:
- primary user or actor
- problem and desired outcome
- explicit non-goals
- success criteria
- core happy path
- important edge/failure states
- constraints and risk modifiers
design
Required branches:
- candidate approaches
- chosen direction and why
- rejected alternatives and why
- boundaries and interfaces
- state/data flow
- failure modes
- reversibility and migration
- verification strategy
domain
Required branches:
- canonical terms
- term definitions
- relationships between terms
- overloaded or conflicting terms
- boundary scenarios
- code/doc contradictions, if a repo exists
- doc target:
CONTEXT.md, ADR, glossary, or no docs
Do not update CONTEXT.md or ADRs unless the user explicitly asks for
docs-mode updates. By default, write candidates into clarity-summary.md.
plan
Required branches:
- acceptance criteria
- task dependencies
- blocking decisions
- validation evidence
- rollback/recovery
- ownership or handoff
- out-of-scope work
Q&A Log Format
Append entries under ## Q&A:
### Q<N>: <short branch title>
- mode: <mode>
- branch: <branch id or name>
- status: resolved | ambiguous | assumption | deferred
- asked: <question>
- recommended: <recommended answer>
- answer: <user answer or discovered evidence>
- rationale: <why this resolves or does not resolve ambiguity>Maintain ## Open Ambiguities as the current queue. Remove resolved items.
Auditor Contract
Send the auditor:
- full
qa-log.md - mode
- current branch, if any
- question count since last audit
Auditor returns:
CONTINUEwith material ambiguities and suggested next question, orSUFFICIENTwith remaining non-blocking assumptions.
Only stop as complete when the auditor says SUFFICIENT or the user explicitly
stops. If the user stops early, set status to paused.
Handoff
After SUFFICIENT, write clarity-summary.md and present one next action:
| Mode | Default Handoff |
|---|---|
requirements | $hoyeon-specify --context .hoyeon/clarify/<topic>/clarity-summary.md "<topic>" |
design | $hoyeon-blueprint --context .hoyeon/clarify/<topic>/clarity-summary.md or ADR candidate |
domain | docs/glossary update, if requested |
plan | $hoyeon-blueprint or direct execution planning |
Do not run the handoff workflow unless the user asks.
Hard Rules
- No implementation.
- No final
requirements.md,plan.json, or ADR unless explicitly requested. - One question at a time.
- Recommended answer required for each user-facing question.
- Record each exchange before asking the next question.
- Continue until
SUFFICIENT,paused, or explicit user stop.
© team-attention, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in skills/clarify of team-attention/hoyeon.
- SKILL.md
- templates/clarity-summary.md
- templates/qa-log.md
Open the folder on GitHubat commit 7cff032
Compare with similar skills
Clarify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clarify this skillteam-attention/hoyeon | 173 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 103k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Grillingpietheinstrengholt/rssmonster | 564 | 32 repos | ~510 | Automated safety check: Pass | MIT | |
| Agentic Workflow Designerdotnet/Open-XML-SDK | 4.6k | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Ask User QuestionMemTensor/MemOS | 12k | — | ~1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
Grilling
pietheinstrengholt/rssmonster
Grill the user relentlessly about a plan, decision, or idea.
- Official
Agentic Workflow Designer
dotnet/Open-XML-SDK
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
Ask User Question
MemTensor/MemOS
Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.
Brainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
More from team-attention/hoyeon
All 36 skills in this repoSkill Session Analyzer
team-attention/hoyeon
This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…
Browser Work
team-attention/hoyeon
Recon-first browser automation. An agent skill from team-attention/hoyeon.
Check
team-attention/hoyeon
This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.
Compound
team-attention/hoyeon
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.
QA
team-attention/hoyeon
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.
Dev Scan
team-attention/hoyeon
Collect diverse opinions on technical topics from developer communities.
Related
Categories
Questions about Clarify
What does Clarify do?
"/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변…. Clarify is an agent skill from team-attention/hoyeon. "/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변 기록", "요구사항 명확화", "설계 명확화".
When should I use Clarify?
Clarify fits situations like: tasks that involve Requirements gathering.
How do I install Clarify in Claude Code?
Run `npx skills add team-attention/hoyeon --skill clarify -a claude-code`. Or copy the skill folder (skills/clarify in team-attention/hoyeon) into .claude/skills/clarify in your project. Claude Code loads it when a task matches its description.
How do I install Clarify in Codex?
Run `npx skills add team-attention/hoyeon --skill clarify -a codex`. Or copy the skill folder (skills/clarify in team-attention/hoyeon) into .agents/skills/clarify in your project. Codex loads it when a task matches its description.
Can I use Clarify in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add team-attention/hoyeon --skill clarify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clarify, .gemini/skills/clarify, .github/skills/clarify and .opencode/skills/clarify in your project.
What does Clarify need to run?
SKILL.md names no scripts, command-line tools or credentials: Clarify is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob, Task, Write, Edit, AskUserQuestion.
Does Clarify access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Clarify safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Clarify use?
Clarify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clarify use?
About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Clarify?
Skills that share tags, products or a category with Clarify: Using Superpowers (farm-fe/farm, 5.6k stars), Interview Me (addyosmani/agent-skills, 103k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars) and Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clarify?
team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.
Source: team-attention/hoyeon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.