codex/skills/hoyeon-clarify/SKILL.md
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로 정리".
npx skillsauth add team-attention/hoyeon hoyeon-clarifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is the Codex-facing wrapper for Hoyeon's canonical clarify skill.
Canonical skill:
__HOYEON_PLUGIN_ROOT__/skills/clarify/SKILL.mdskills/clarify/SKILL.md from the current Hoyeon repoWhen this skill is invoked:
.hoyeon/clarify/<topic-slug>/.hoyeon-clarity-auditor at audit boundaries when native adapters are
loaded. If unavailable, do a compact direct audit and record the fallback.hoyeon-code-explorer when code/docs can answer a question better than
the user can.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.
development
Run a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke test, run checks, validate a feature, inspect a local app in the browser, capture screenshots, or turn discovered QA issues into regression tests/checklists with user approval.
development
Hoyeon execution workflow for Codex. Use when the user invokes "$hoyeon-execute" or wants to execute a Hoyeon plan.json through the Bash-first Codex adapter. This adapter loads the canonical execute skill and follows its Codex runtime surface.
development
Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"
testing
"/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.