team-attention-hoyeon

Plugin team-attention-hoyeon from marketplace cascade-code-testing-misc in joshuarweaver/cascade-code-testing-misc. Commands read from the repo's manifest — 1 month ago.

Skills (37)

• hoyeon-blueprint

  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-browser-work

  Hoyeon browser automation workflow for Codex. Use when the user invokes "$hoyeon-browser-work" or asks Codex to perform a browser task through recon-first chromux automation. This adapter loads the canonical browser-work skill and follows its Codex runtime surface.

• hoyeon-clarify

  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-deep-research

  Hoyeon deep research workflow for Codex. Use when the user invokes "$hoyeon-deep-research" or wants a multi-channel cited research report using web search, browser extraction, and optional Gemini. This adapter loads the canonical deep-research skill and follows its Codex runtime surface.

• hoyeon-dev-scan

  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-discuss

  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 "같이 생각해보자", "문제 정의", "이거 어떻게 생각해?", "요구사항이 불명확

• hoyeon-execute

  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.

• hoyeon-google-search

  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-reference-seek

  Hoyeon implementation reference discovery workflow for Codex. Use when the user invokes "$hoyeon-reference-seek" or asks for internal patterns, open-source references, GitHub examples, official docs, or comparable implementations. This adapter loads the canonical reference-seek skill and follows its

• hoyeon-specify

  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.

• analyze-oss

  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 OS

• blueprint

  /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 /spe

• browser-work

  Recon-first browser automation. Orchestrator explores the site first via chromux, saves a guide file with insights, then delegates execution to browser-explorer agent. Use when: "/browser-work", "브라우저 작업", "사이트에서 해줘", "웹에서 해줘", "LinkedIn에서", "크롬으로", "browser task", "automate this site".

• bugfix

  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. - Read - Grep - Glob - Task - Bash - Edit - Write - AskUserQuestion -

• check

  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. E

• clarify

  /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/cla

• compound

  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/. - Read - Grep - Glob - Bash - Write - Edit - AskUserQuestion

• council

  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 opin

• deep-research

  Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch research agents AND browser-explorer agents (via chromux for JS-heavy/dynamic sites), plus a Gemini CLI deep research source, then synthesizes everything into a cited report. Uses WebSearc

• dev-scan

  Collect diverse opinions on technical topics from developer communities. Use for "developer reactions", "community opinions" requests. Aggregates Reddit, HN, Dev.to, Lobsters, ProductHunt, etc.

• discuss

  /discuss", "discuss this", "think with me", "is this a good idea?", "what do you think about", "problem definition", "explore this idea", "/discuss --scored", "interview me", "clarify requirements", "요구사항 정리", "인터뷰", "딥 인터뷰", "뭘 만들어야 할지 모르겠어", Korean triggers: "같이 생각해보자", "이거 어떻게 생각해?", "문제 정의", "이게

• execute

  Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행" - Read - Grep - Glob - Bash - Edit - Write - TaskCreate - TaskUpdate - TaskList - TaskGet - TaskOutput - AskUserQues

• google-search

  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 arti

• issue

  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 만들자", "깃헙 이슈" - Read - Grep - Glob - Bash - Agent - AskUserQ

• mirror

  /mirror", "mirror back", "echo back", "다시 설명해줘", "이해한 거 맞아?", "내가 뭘 원하는지 말해봐", "확인해줘", "paraphrase this", "너가 이해한 거 설명해봘", "what did I ask?" - AskUserQuestion - Read - Grep - Glob Must contain Mirror Back with What/Why/Scope/Constraints. Must reach CONFIRMED or user-initiated exit. Must NOT generate

• qa

  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

• ralph

  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

• reference-seek

  This skill should be used when the user asks to "find references", "참고할 만한 거", "similar implementation", "오픈소스 있나", "how others do this", "레퍼런스 찾아줘", or needs to find existing patterns (internal) and open-source examples (external) for implementing a feature. Must contain all of these sections: - In

• rulph

  Iterative rubric-based evaluation and self-improvement loop. Builds a scoring rubric interactively, evaluates an artifact with multiple models in parallel (Codex, Gemini, Claude), then autonomously improves the artifact one criterion at a time until a score threshold is met or circuit breaker fires.

• scaffold

  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, rule

• skill-session-analyzer

  This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions to validate skill/agent/hook b

• specify

  /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).

• stepback

  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", "한발 물

• tech-decision

  This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions. Provide

• tribunal

  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 synthesiz

• ultrawork

  This skill should be used when the user says "/ultrawork", "ultrawork", or wants to run the full specify → execute pipeline automatically with a single command. Automated end-to-end workflow that chains specify and execute skills. - Read - Grep - Glob - Task - Write - Bash - Edit - Skill - AskUserQu

• verify

  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.

Subagents (30)

• _karpathy

  Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

• browser-explorer

  Browser Explorer agent that controls the real Chrome browser via chromux (raw CDP). Parallel-safe — each agent gets its own isolated tab. Uses an isolated Chrome profile (logins persist across sessions, no bot detection). Use when you need to explore external web services (Crisp, Reddit, dashboards,

• business-extractor

  Extract business requirements from Q&A log. PM perspective — WHO/WHY/WHAT/SUCCESS/SCOPE/RISK.

• clarity-auditor

  Audits clarify Q&A logs for remaining material ambiguity across requirements, design, domain, and plan modes.

• code-explorer

  Fast, read-only codebase search specialist. Finds files, code patterns, and relationships. Use for: "where is X?", "which files contain Y?", "how does X connect to Y?", "what changed recently in Z?", "find all usages of W". NOT for: documentation search (docs-researcher), external APIs (external-res

• code-reviewer

  Code reviewer that performs systematic cross-cutting review of complete diffs. Catches integration issues, hidden bugs, and design inconsistencies that per-task verification misses. Returns SHIP or NEEDS_FIXES verdict. - Write - Edit - Task - NotebookEdit Must contain a Code Review Report with: 1. V

• codex-risk-analyst

  Codex-powered risk analyst for /tribunal skill. Finds vulnerabilities, failure modes, edge cases, and architectural risks. The adversarial voice. - Write - Edit - Task - NotebookEdit Must contain a Risk Analysis Report with: 1. Critical Risks (show-stoppers) 2. Moderate Risks (need mitigation) 3. Ed

• codex-strategist

  Calls OpenAI Codex CLI to synthesize multiple analysis reports and provide big-picture strategic review. Cross-checks gap analysis, tradeoff analysis, verification planning, and external research for contradictions and blind spots. - Write - Edit - Task - NotebookEdit Must contain a Codex Strategic

• contract-deriver

  Derive cross-module agreements (types, interfaces, invariants) from requirements.md. Writes a single `contracts.md` artifact (markdown, language-agnostic). Called by /blueprint Phase 1.

• debugger

  Root cause analysis specialist. Traces bugs backward through call stack, classifies bug type, recommends minimal fix. Read-only investigation only. Use this agent when a bug needs diagnosis before fixing. - Write - Edit - Task Must contain all sections of Bug Analysis Report: 1. Bug Type classificat

• docs-researcher

  Searches project internal docs (ADRs, READMEs, configs) for architecture decisions, team conventions, and constraints relevant to the current task.

• external-researcher

  Researches external libraries, frameworks, and best practices via web search and official docs. Use for migrations, new tech decisions, and unfamiliar APIs.

• feasibility-checker

  Feasibility checker for /tribunal skill. Evaluates whether the proposal is practically achievable given constraints. The pragmatic voice. - Write - Edit - Bash - Task - NotebookEdit Must contain a Feasibility Report with: 1. Technical Feasibility 2. Resource/Effort Assessment 3. Dependencies 4. Feas

• gap-analyzer

  Gap analysis agent that identifies missing requirements, potential pitfalls, and explicit "must NOT do" items before plan generation. Inspired by Metis from oh-my-opencode.

• gap-auditor

  Interview quality auditor that checks Q&A coverage and identifies gaps. Use after each axis interview round to determine if more questions are needed.

• git-master

  Git commit specialist. Enforces atomic commits, detects project style. Use this agent for ALL git commits during /execute workflow. Triggers: "commit", "git commit" - Bash - Read - Grep - Glob - Task - Write - Edit Must create atomic commits and output COMMIT SUMMARY: - STYLE DETECTION RESULT: detec

• interaction-extractor

  Extract interaction requirements from Q&A log. Interpreted per project-type (user/developer/operator/consumer experience) — JOURNEY/HAPPY/EDGE/STATE/FEEDBACK/ACCESS.

• interviewer

  Socratic interviewer - questions only, no code, no implementation

• qa-verifier

  Spec-driven QA verification agent. Reads sub-requirements (GWT format) from requirements.md/plan.json, determines the appropriate verification method for each (browser/CLI/desktop/shell), executes verification, and returns structured PASS/FAIL per sub-requirement. Does NOT fix code — report only. Us

• ralph-verifier

  Independent DoD verifier for /ralph skill. Runs in a separate context to eliminate self-verification bias. Reads the DoD checklist and independently checks each item against actual code, test results, and file state. Returns structured PASS/FAIL per item. Read-only — does not modify any project file

• spec-coverage

  Sub-requirement spec-coverage reviewer for the execute verify pipeline. Checks whether a single sub_req's Given/When/Then contract is semantically satisfied by the submitted diff and cites the file:line that satisfies each of given, when, and then. Complements code-reviewer at gate=2 (code-reviewer

• taskgraph-planner

  Produce a layered task DAG (L0 Foundation → L1 Feature → L2 Integration → L3 Deploy) where every sub-requirement is fulfilled by ≥1 task. Marks parallelism explicitly. Called by /blueprint Phase 2.

• tech-extractor

  Extract technical requirements from Q&A log. Tech Lead perspective — ARCH/DATA/INFRA/DEPEND/COMPAT/SECURITY.

• tradeoff-analyzer

  Evaluates proposed changes for risk (LOW/MED/HIGH), simpler alternatives, over-engineering, and generates structured decision_points for human approval on dangerous changes.

• ux-reviewer

  UX review agent that evaluates how proposed changes affect existing user experience. Focuses on simplicity, intuitiveness, and preventing UX regression. Runs early in the specify flow to ensure UX direction is solid before technical planning begins.

• value-assessor

  Value assessor for /tribunal skill. Evaluates positive impact, goal alignment, and strengths of the proposal. The constructive voice. - Write - Edit - Bash - Task - NotebookEdit Must contain a Value Assessment Report with: 1. Goal Alignment 2. Key Strengths 3. Value Delivered 4. Value Summary with r

• verification-planner

  Explore the project's test infrastructure and establish a verification strategy for sub-requirements using the 2-axis model (machine-verifiable vs agent-verifiable)

• verifier

  Independent sub-requirement verifier. Executes verify_plan entries mechanically — no judgment, no bypass.

• verify-planner

  Assign verification gates (1=machine, 2=agent_semantic, 3=agent_e2e, 4=human) to every sub-requirement and every journey. Uses semantic reading of given/when/then — not keyword matching. Called by /blueprint Phase 4.

• worker

  Implementation worker agent. Handles code writing, bug fixes, and test writing. Only works on tasks delegated by Orchestrator (/execute skill). Use this agent when you need to delegate implementation work during plan execution. - Read - Grep - Glob - Write - Edit - Bash - WebSearch - WebFetch - Task

Hooks (20)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/cli-version-sync.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/session-compact-hook.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/skill-session-init.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/rulph-init.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/skill-session-guard.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/ralph-dod-guard.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/validate-output.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/tool-output-truncator.sh

• PostToolUseFailure

  ${CLAUDE_PLUGIN_ROOT}/scripts/edit-error-recovery.sh

• PostToolUseFailure

  ${CLAUDE_PLUGIN_ROOT}/scripts/large-file-recovery.sh

• PostToolUseFailure

  ${CLAUDE_PLUGIN_ROOT}/scripts/tool-failure-tracker.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/scripts/ultrawork-stop-hook.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/scripts/skill-session-stop.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/scripts/rv-validator.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/scripts/rulph-stop.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/scripts/ralph-stop.sh

• SessionEnd

  ${CLAUDE_PLUGIN_ROOT}/scripts/skill-session-cleanup.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/scripts/ultrawork-init-hook.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/scripts/skill-session-init.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/scripts/rv-detector.sh

Similar plugins