hoyeon-blueprint
Hoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a…
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 -y skills add team-attention/hoyeon --skill hoyeon-clarify --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/hoyeon-clarifyContext preview
The summary Claude sees to decide when to auto-load this skill.
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로 정리".
name: hoyeon-clarify description: | 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로 정리".
This is the Codex-facing wrapper for Hoyeon's canonical `clarify` skill.
Canonical skill:
When this skill is invoked:
1. Read the canonical skill file above before executing the workflow. 2. Follow the one-question-at-a-time ambiguity-resolution loop. 3. Write Q&A state under `.hoyeon/clarify/<topic-slug>/`. 4. Use `hoyeon-clarity-auditor` at audit boundaries when native adapters are loaded. If unavailable, do a compact direct audit and record the fallback. 5. Use `hoyeon-code-explorer` when code/docs can answer a question better than the user can. 6. 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`.
All you need is requirements. A Claude Code plugin that derives requirements from your intent, verifies every derivation, and delivers traced code — without you writing a plan. AI can build anything. The hard part is knowing what to build — precisely.
Hoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a…
Hoyeon browser automation workflow for Codex. Use when the user invokes "$hoyeon-browser-work" or asks Codex to perform a browser…
Hoyeon deep research workflow for Codex. Use when the user invokes "$hoyeon-deep-research" or wants a multi-channel cited…
Hoyeon developer community scan workflow for Codex. Use when the user invokes "$hoyeon-dev-scan" or asks for developer reactions,…
Hoyeon Socratic discussion workflow for Codex. Use when the user invokes "$hoyeon-discuss", "/discuss", asks to think through an…
Hoyeon execution workflow for Codex. Use when the user invokes "$hoyeon-execute" or wants to execute a Hoyeon plan.json through…