team-attention/hoyeon-discuss
codex/skills/hoyeon-discuss/SKILL.md
Hoyeon Socratic discussion workflow for Codex. Use when the user invokes "$hoyeon-discuss", "/discuss", asks to think through an idea, challenge assumptions, clarify requirements before planning, run a deep/scored discussion, or says Korean phrases like "같이 생각해보자", "문제 정의", "이거 어떻게 생각해?", "요구사항이 불명확", or "아이디어 구체화".
$ install --global
skillsauthnpx skillsauth add team-attention/hoyeon hoyeon-discussInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 16, 2026, 4:36 AM141.8s1 file scanned
SKILL.md
- name:
- hoyeon-discuss
- description:
- |
hoyeon-discuss
This is the Codex-facing wrapper for Hoyeon's canonical discuss skill.
Canonical skill:
- Installed root:
__HOYEON_PLUGIN_ROOT__/skills/discuss/SKILL.md - Repo-local fallback:
skills/discuss/SKILL.mdfrom the current Hoyeon repo
When this skill is invoked:
- Read the canonical skill file above before executing the workflow.
- Follow its DIAGNOSE -> PROBE -> SYNTHESIZE flow.
- Stay in discussion mode: challenge assumptions, surface blind spots, and help the user clarify the idea before implementation planning.
- Do not generate
PLAN.md, mutateplan.json, run implementation, or prescribe a solution as the main output. - For
--deep, dispatchhoyeon-code-explorerfor codebase context when native adapters are loaded. If unavailable, do the smallest read-only local exploration directly and report the fallback. - For
/specifyhandoff, point the user to$hoyeon-specifyand pass along the generated.hoyeon/discuss/<topic-slug>/insights.mdcontext when saved. - Use Codex-native user interaction. If a structured question tool is not available in the current mode, ask the same decision question in concise plain text and continue from the user's answer.
The output contract remains the canonical Hoyeon contract:
discussion insights in conversation, optionally saved to
.hoyeon/discuss/<topic-slug>/insights.md, with a handoff suggestion to
$hoyeon-specify only after synthesis.
Related Skills
team-attention/verify
development
VerifiedTrustedCommunity
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.
161SKILL.mdUpdated May 22, 2026
team-attention/hoyeon-execute
development
VerifiedTrustedCommunity
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.
161SKILL.mdUpdated May 16, 2026
team-attention/execute
development
VerifiedTrustedCommunity
Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"
161SKILL.mdUpdated Apr 15, 2026
team-attention/clarify
testing
VerifiedTrustedCommunity
"/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.
159SKILL.mdUpdated May 16, 2026