agmo-everywhere

Loaded automatically at session start. Teaches the orchestrator how to route requests to skills and agents. Do not invoke manually.

Use when the user wants to explore an idea, design an approach, or think through a problem before implementing. Triggers on "고민", "논의", "아이디어", "brs".

Use when code review is needed. Triggers on "코드 리뷰", "리뷰해줘", "code review", or at completion of implementation.

Use to harvest `debt:` markers across the repo into a debt ledger and optionally persist it to the Obsidian vault. Triggers on "부채", "기술부채", "debt", "지름길 정리", "/debt". Read-only — does not modify code.

Use when the user wants to run an implementation plan. Triggers on "실행해줘", "구현해줘", "시작해줘", "execute", or after plan approval.

Implement an entire Figma page as Android Jetpack Compose screens by auto-splitting into frames with visual verification. Use whenever a user shares a figma.com/design URL and wants the page built as Compose code. Triggers on '안드로이드 피그마', 'Android Figma', 'Compose 구현'. Covers any multi-frame page. Does NOT apply to Figma asset downloads or single component edits.

Implement an entire Figma page by auto-splitting into frames with visual verification. Use whenever a user shares a figma.com/design URL and wants the page built in code. Triggers on '피그마 구현', '피그마 페이지', 'Figma implement'. Covers any multi-frame page: landing, dashboard, marketing, etc. Does NOT apply to Figma asset downloads or single component edits.

Use to analyze plugin usage patterns and suggest improvements. Triggers on "플러그인 리뷰", "plugin review", "사용 패턴 분석".

Use to audit and repair the llm-wiki context spine by detecting stale, low-confidence, contested, or broken entries. Triggers on "위키 점검", "wiki maintain", "wiki audit", "컨텍스트 정리", "wiki 오염", "모순 감지".

Use to save implementation summary to Obsidian vault. Auto-triggered after execute completes. Triggers on "구현 저장", "작업 정리", "save impl".

Use for first-time plugin configuration. Triggers on "setup", "설정", "초기 설정".

Use to search Obsidian vault by keyword. Triggers on "옵시디언에서 찾아", "vault 검색", "관련 노트", "이전에 작성한", "예전에 정리한".

Use to record a significant learning, decision, or issue to Obsidian vault. Triggers on "기억해", "이거 기록해", "wisdom", or when a significant learning occurs during debugging/verification.

Use to run benchmarks, save results to Obsidian vault, and detect regressions against a baseline. Triggers on "벤치마크", "benchmark", "성능 측정".

Use for systematic debugging. Auto-triggered when verification fails 3 times. Triggers on "디버깅", "debug", "왜 안 돼".

Use for git operations — commit, PR, branch management. Triggers on "커밋", "commit", "PR 만들어", "브랜치".

Use to generate a weekly retrospective by analyzing git log. Triggers on "회고", "retro", "이번 주 정리". Only runs on explicit user request — never auto-triggered.

Use to perform a security audit of the codebase. Triggers on "보안 점검", "security audit". Delegates to architect agent.

Use to verify a claim of completion with evidence. Auto-triggered after each TODO in execute. Triggers on "검증", "verify", "확인해줘".

Use when a plan needs validation through a planner-critic loop. Triggers on "플랜 리뷰", "plan review", or when explicitly requested.

Create a GitHub Issue following org templates (Feature/Task/Bug), auto-map to GitHub Project, auto-assign current gh user, and link parent for Task issues. Triggers on "이슈 만들어", "이슈 생성", "깃허브 이슈", "create issue", "new issue", "피처 이슈", "태스크 이슈", "버그 이슈", "이슈 발행". Use this when creating issues from conversation context or user input. If the user references an Obsidian note as the source, use note-to-issue instead.

Use to convert an Obsidian note into a GitHub Issue. Triggers on "노트로 이슈 만들어", "이슈로 변환", "이거 이슈로", "노트 이슈화". Only use when user explicitly references an Obsidian note as the source. For creating issues from conversation context (without a note), use create-issue instead.

Use to dispatch multiple independent TODOs concurrently. Invoked by execute skill when independent TODOs are detected.

Use when the user needs a structured implementation plan with concrete TODOs. Triggers on "플랜", "계획", "plan", or after brainstorming completes.

Persistent execution loop that continues until all work is verified complete. Auto-linked by execute skill. Triggers on "끝까지 해줘", "멈추지 마", "ralph".

Use when the user wants to stop current execution. Triggers on "취소", "중단", "그만", "cancel", "stop".

Fallback for when the plan skill's auto-save fails or is skipped. Use to manually save a plan to Obsidian vault. Triggers on "플랜 저장", "save plan".

Use to verify WCAG accessibility compliance of frontend/UI code. Auto-triggered by execute when TODO has frontend/ui tags. Triggers on "접근성", "accessibility", "WCAG".

Use to save a design, research, meeting, or memo note to Obsidian vault. Triggers on "옵시디언에 저장", "노트 저장", "기록해줘", "정리해줘".

Use when implementing with test-driven development. Triggers on "TDD", "테스트 먼저", "test first", or when the plan specifies TDD.