team-attention/hoyeon-specify
codex/skills/hoyeon-specify/SKILL.md
Hoyeon requirements workflow for Codex. Use when the user invokes "$hoyeon-specify" or wants to turn an unclear goal into structured requirements.md for Hoyeon. This adapter loads the canonical specify skill and follows its Codex runtime surface.
$ install --global
skillsauthnpx skillsauth add team-attention/hoyeon hoyeon-specifyInstall 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 AM121.1s1 file scanned
SKILL.md
- name:
- hoyeon-specify
- description:
- |
hoyeon-specify
This is the Codex-facing wrapper for Hoyeon's canonical specify skill.
Canonical skill:
- Installed root:
__HOYEON_PLUGIN_ROOT__/skills/specify/SKILL.md - Repo-local fallback:
skills/specify/SKILL.mdfrom the current Hoyeon repo
When this skill is invoked:
- Read the canonical skill file above before executing the workflow.
- Follow the
Runtime Surface->Codexsection in that file. - Keep durable state changes Bash-first through
hoyeon-cli. - Do not rely on hooks or MCP for Codex v1.
- Use Hoyeon native-agent adapter names when dispatching subagents:
hoyeon-code-explorer,hoyeon-worker,hoyeon-verifier, andhoyeon-code-reviewer.
Interview obligation (Codex)
The canonical skill is written around the AskUserQuestion tool, which Codex
does not have. Lack of AskUserQuestion is NOT a license to skip the
interview. You must still elicit user intent before writing
requirements.md.
Rules:
- Ask one concise plain-text question at a time. Wait for the user's reply before continuing. Do not batch multiple questions into one turn unless they are trivially orthogonal yes/no items.
- Phase 0.1 Mirror is mandatory — present your understanding (goal, non-goal, ambiguous) and ask the user to approve or revise before proceeding.
- Phase 0.2 WHERE inference is mandatory — infer
PROJECT_TYPE,SITUATION,AMBITION,RISK factorsfrom the repo, present the "Inferred Context" block with evidence and confidence, and ask the user to confirm or override. - Any dimension marked low confidence (typically
AMBITIONon a truly new project) MUST be asked explicitly. Do not silently default. - Phase 1 axis interviews still apply. Convert each
AskUserQuestionprompt in the canonical skill into a plain-text question that lists the same options inline (e.g., "Who is the primary user? (a) Senior developers, (b) Junior developers, (c) Both — or describe your own."). - Phase 4 Confirmation is mandatory — show the requirements preview
and get explicit user approval before overwriting
requirements.md.
If the user repeatedly answers "you decide" or "whatever works", follow the canonical "I don't know" protocol (tentative judgment + Open Decision entry), not silent inference.
The output contract remains the canonical Hoyeon contract:
<spec_dir>/requirements.md.
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