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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze an open-source project from What/Why perspective (not how-it's-implemented). Use when the user says "/analyze-oss", "분석해줘 이 오픈소스", "이 레포 뭐하는거야", "analyze this repo", "what does X do", "이거 왜 쓰는거야", "이 라이브러리 분석", provides a GitHub URL and wants understanding, or asks to deeply understand an OSS project's purpose, value, target users, and usage flow. Clones the repo to ~/opensource-analysis/<repo-name>/ (git pull if already exists), dispatches parallel subagents per analysis lens, then synthesizes a What/Why-focused report in chat. Supports optional user-specific follow-up questions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists. Phase 1: validate changed files against .hoyeon/rules/ checklists and report PASS/WARN. Phase 2 (conditional): propose rule additions when unmatched patterns are detected. Essential before git push. Trigger phrases: "check", "checklist", "verify changes", "what did I miss", "pre-push check", "cascading changes", "any more changes needed", "update checklist", "update rules", "rules update", "체크", "체크리스트", "변경 확인", "빠뜨린 거 없나", "push 전 확인", "뭐 더 건드려야 해?", "연쇄 변경 확인", "규칙 갱신".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. Extracts knowledge from PR context and saves to docs/learnings/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user says "/council", "council", "deliberate", "multi-perspective decision", "트레이드오프 분석", "위원회 소집", "여러 관점으로 검토", or wants deep multi-perspective deliberation with tradeoff mapping. Combines tribunal (structured adversarial review), agent-council (external LLM opinions), dev-scan (community sentiment), and step-back (meta-level review) into a unified decision-making committee. Uses Agent Teams for real peer-to-peer debate with iterative step-back moderation loop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Google search via real Chrome browser (chromux). Use when the user asks to "search Google", "구글 검색", "구글에서 찾아줘", "find articles about", "search the web for", or needs web search results with full page content. Also trigger when: searching a specific site ("search dev.to for..."), finding recent articles/posts about a topic, extracting content from search results, or when WebSearch results are insufficient and real browser rendering is needed. Prefer this over WebSearch when the user wants site-specific search, time-filtered results, or full article body/comments extraction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. Three modes: browser (chromux/CDP, fast, DOM-level), computer (MCP computer-use, screenshot + pixel clicks, any app), and cli (tmux, send-keys + capture-pane for interactive terminals). Auto-selects mode or accepts --browser / --computer / --cli override. Use when asked to "qa", "QA", "test this site", "test this app", "find bugs", "test and fix", "fix what's broken", "dogfood", "exploratory test", "bug hunt", "QA this app", "사이트 테스트", "앱 테스트", "브라우저 QA", "화면 보고 테스트해줘", "네이티브 앱 테스트", "screen test". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iterative task completion loop with Definition of Done verification. Combines the Ralph Wiggum technique (prompt re-injection via Stop hook) with DoD-based independent verification. Claude proposes DoD criteria, user confirms, then Claude works autonomously. Stop hook re-injects the original prompt and blocks exit until all DoD items are independently verified. "/ralph", "ralph loop", "ralph 루프", "반복 작업", "DoD 루프", "완료 검증 루프", "task loop", "keep going until done"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"/specify", "specify", "요구사항 정의", "requirements", "스펙 잡기", "뭘 만들어야 하는지", "기획 정리", "인터뷰해서 스펙" Turn a goal into structured requirements through systematic interview. Three phases: Interview → Extract → Cross-check. Writes requirements.md in the cli format (consumed by /blueprint).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review. Also triggered by: "트리뷰널", "리뷰 해줘", "3관점 리뷰", "위험성 검토". Runs 3 agents (Risk/Value/Feasibility) in parallel and synthesizes a verdict.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a validated plan.json and optional contracts.md. This adapter loads the canonical blueprint skill and follows its Codex runtime surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hoyeon developer community scan workflow for Codex. Use when the user invokes "$hoyeon-dev-scan" or asks for developer reactions, community opinions, or cross-community sentiment on technical topics. This adapter loads the canonical dev-scan skill and follows its Codex runtime surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hoyeon Google/chromux search workflow for Codex. Use when the user invokes "$hoyeon-google-search" or needs real-browser Google search, site-specific search, time filters, or body/comment enrichment. This adapter loads the canonical google-search skill and follows its Codex runtime surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"/blueprint", "blueprint", "task graph", "contract derivation", "execution plan", "plan tasks from requirements", "contract-first planning" Turn requirements.md into an executable blueprint (plan.json + contracts.md). Five phases: Contracts → Tasks → Journeys → Verify Plan → Commit. Sits between /specify and /execute. Scope-adaptive (greenfield → bugfix). Uses hoyeon-cli (plan.json only; requirements.md is read as-is via Read tool).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Root cause based one-shot bug fix. debugger diagnosis → requirements.md generation → /execute. /bugfix "error description" Full investigation pipeline: debugger + gap-analyzer + standard verify. QA suggestion after successful fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GitHub issue creation skill. Analyzes the entire codebase impact based on user request, then creates a structured issue with AI-verified/human-judgment-needed/caution sections. /issue "issue description" Trigger: "/issue", "이슈 만들어", "issue 만들자", "깃헙 이슈"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"/mirror", "mirror back", "echo back", "다시 설명해줘", "이해한 거 맞아?", "내가 뭘 원하는지 말해봐", "확인해줘", "paraphrase this", "너가 이해한 거 설명해봘", "what did I ask?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Greenfield project architecture + harness scaffolding for AI Agent productivity. Interview-driven decisions → requirements.md → execute. Produces: Code Structure (vertical slice exemplar), Test Infrastructure, Guard Rails, conditional extensions, AND Harness (CLAUDE.md with domain/team context, rules, skills, hooks). L2: architecture decisions, L3: harness setup, L4: requirements + harness decisions (tasks generated later by /execute into plan.json). Use when: "/scaffold", "scaffold", "new project", "set up project", "프로젝트 세팅", "초기 구조"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
One-shot perspective reset that surfaces blind spots mid-work. Scans what the user has been doing, generates one abstract reframing question, and runs 3 quick checks (scope drift, side effects, better approach) in under 10 lines. No dialogue, no code. Trigger phrases: "/stepback", "step back", "한발 물러서", "넓은 관점", "놓치는 거 없나", "방향 맞나", "zoom out", "큰 그림", "방향이 맞는 거야", "잠깐 멈춰", "지금 뭘 하고 있는 거야", "blind spot", "재확인"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 "아이디어 구체화".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.