Hoyeon ambiguity-resolution interview for Codex. Use when the user invokes
"$hoyeon-clarify", "/clarify", asks to keep asking until clear, remove
ambiguity, clarify requirements/design/domain/plan, or says Korean phrases
like "๋ชจํธํ ๊ฒ ์๊ฒ", "๋ช ํํด์ง ๋๊น์ง", "์ง๋ฌธ ๊ณ์ํด", or "Q&A๋ก ์ ๋ฆฌ".
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Hoyeon ambiguity-resolution interview for Codex. Use when the user invokes
"$hoyeon-clarify", "/clarify", asks to keep asking until clear, remove
ambiguity, clarify requirements/design/domain/plan, or says Korean phrases
like "๋ชจํธํ ๊ฒ ์๊ฒ", "๋ช ํํด์ง ๋๊น์ง", "์ง๋ฌธ ๊ณ์ํด", or "Q&A๋ก ์ ๋ฆฌ".
hoyeon-clarify
This is the Codex-facing wrapper for Hoyeon's canonical clarify skill.
Repo-local fallback: skills/clarify/SKILL.md from the current Hoyeon repo
When this skill is invoked:
Read the canonical skill file above before executing the workflow.
Follow the one-question-at-a-time ambiguity-resolution loop.
Write Q&A state under .hoyeon/clarify/<topic-slug>/.
Use hoyeon-clarity-auditor at audit boundaries when native adapters are
loaded. If unavailable, do a compact direct audit and record the fallback.
Use hoyeon-code-explorer when code/docs can answer a question better than
the user can.
Do not implement, write final requirements.md, mutate plan.json, or
create ADRs unless the user explicitly asks for that handoff.
The output contract remains the canonical Hoyeon contract:
.hoyeon/clarify/<topic-slug>/qa-log.md and, when sufficient,
.hoyeon/clarify/<topic-slug>/clarity-summary.md.
