team-attention/hoyeon

1

bugfix Root cause based one-shot bug fix. debugger diagnosis → requirements.md generation → /execute. /bugfix "error descrip…

team-attention/hoyeon

4

2

check This skill should be used when the user wants to verify their changes before pushing, or update the project's rule ch…

team-attention/hoyeon

4

3

council This skill should be used when the user says "/council", "council", "deliberate", "multi-perspective decision", "트레…

team-attention/hoyeon

4

4

discuss "/discuss", "discuss this", "think with me", "is this a good idea?", "what do you think about", "problem definition",…

team-attention/hoyeon

4

5

google-search Google search via real Chrome browser (chromux). Use when the user asks to "search Google", "구글 검색", "구글에서 찾…

team-attention/hoyeon

4

6

qa Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or…

team-attention/hoyeon

4

7

reference-seek This skill should be used when the user asks to "find references", "참고할 만한 거", "similar implementation", "오픈…

team-attention/hoyeon

4

8

scaffold Greenfield project architecture + harness scaffolding for AI Agent productivity. Interview-driven decisions → require…

team-attention/hoyeon

4

9

specify "/specify", "specify", "요구사항 정의", "requirements", "스펙 잡기", "뭘 만들어야 하는지", "기획 정리", "인터뷰해서 …

team-attention/hoyeon

4

10

browser-work Recon-first browser automation. Orchestrator explores the site first via chromux, saves a guide file with insights, t…

team-attention/hoyeon

3

11

compound This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learne…

team-attention/hoyeon

3

12

deep-research Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch resea…

team-attention/hoyeon

3

13

dev-scan Collect diverse opinions on technical topics from developer communities. Use for "developer reactions", "community op…

team-attention/hoyeon

3

14

execute Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the …

team-attention/hoyeon

3

15

issue GitHub issue creation skill. Analyzes the entire codebase impact based on user request, then creates a structured iss…

team-attention/hoyeon

3

16

mirror "/mirror", "mirror back", "echo back", "다시 설? "내가 뭘 원하는지 말해봐", "확인해줘", "paraphrase this", "너가 이해…

team-attention/hoyeon

3

17

ralph Iterative task completion loop with Definition of Done verification. Combines the Ralph Wiggum technique (prompt re-i…

team-attention/hoyeon

3

18

rulph Iterative rubric-based evaluation and self-improvement loop. Builds a scoring rubric interactively, evaluates an arti…

team-attention/hoyeon

3

19

skill-session-analyzer This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", …

team-attention/hoyeon

3

20

stepback One-shot perspective reset that surfaces blind spots mid-work. Scans what the user has been doing, generates one abst…

team-attention/hoyeon

3

21

tech-decision This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysi…

team-attention/hoyeon

3

22

tribunal This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feas…

team-attention/hoyeon

3

23

ultrawork This skill should be used when the user says "/ultrawork", "ultrawork", or wants to run the full specify → execute pi…

team-attention/hoyeon

3

24

deep-interview "/deep-interview", "deep interview", "interview me", "clarify requirements", "요구사항 정리", "인터뷰", "딥 인터뷰", …

team-attention/hoyeon

2

25

quick-plan "/quick-plan", "quick plan", "태스크 플래닝", "작업 계획", "세션 플래닝", "plan tasks", "what should we do", "작업 정…

team-attention/hoyeon

2

26

scope Fast parallel change-scope analyzer. Launches 5+ agents concurrently to identify what files need changing, what could…

team-attention/hoyeon

2

27

analyze-oss Analyze an open-source project from What/Why perspective (not how-it's-implemented). Use when the user says "/analyze…

team-attention/hoyeon

1

28

blueprint "/blueprint", "blueprint", "task graph", "contract derivation", "execution plan", "plan tasks from requirements", "co…

team-attention/hoyeon

1

29

clarify "/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", …

team-attention/hoyeon

1

30

verify Run a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke t…

team-attention/hoyeon

1