issue-intake
Issueの初期トリアージスキル。Issueを受け取り、標準化された分析結果（分類・深刻度・影響スコープ・不確実性・次アクション参照）を生成する。GitHub/Jira/Linear等のトラッカーからissue_payload形式で受け取る。 トリガー条件: - 「Issue #N を分析して」「このIssueの深刻度は？」「このバグはCritical？」 - 「Issue本文を初期トリアージして」「Issueを取り込んで」 - 新しいIssueを受け取り、最初の分類・判断が必要な時 注意: 根本原因の断定、修正案の確定、優先度の最終決定は行わない（材料提供まで）
bv-integration
Beads Viewer (BV) integration for visual task management and smart task selection. Use for Kanban views, dependency graphs, and the robot-plan API for auto-selecting next tasks. Keywords: beads, viewer, kanban, dependency graph, robot-plan, task selection, bottleneck
writing-plans
계획, 구현 계획, 플랜 작성, 작업 계획, 구현 플랜 - Use when you have a spec or requirements for a multi-step task, before touching code
moai-lang-html-css
Enterprise Skill for advanced development
example-skill
Short summary of what this skill accomplishes.
brainstorming
Diagnose and fix convergent ideation. Use when brainstorming produces the same ideas every time, when all ideas cluster around one approach, or when you need to escape domain defaults.
fix-linear-bugs
Fix Linear issues tagged with "bug". Either produces a PR with the fix or explains why it won't be fixed. Triggers - fix bugs, linear bugs, bug triage, resolve bugs.
ideation
Transform raw brain dumps into structured implementation artifacts. Use when user has messy ideas, scattered thoughts, or dictated stream-of-consciousness about something they want to build. Produces contracts, phased PRDs, and implementation specs written to ./docs/ideation/{project-name}/.
snt-ccu2-host
JIRA 티켓 기반 CCU-2.0 구현 파이프라인. 요구사항 추출, 코드 구현, 빌드, 테스트를 자동화. "파이프라인", "워크플로우", "티켓 구현" 키워드시 활성화
research-plan-implement
A structured workflow for AI-assisted development using research, planning, and systematic implementation phases
project-complete
项目完成导航。触发：用户通知"项目完成"或"可以提交了"时使用；执行归档、生成changelog、git commit+push。
requirements-spec-kit
Spec Kit を使って要件定義や仕様作成（仕様策定・仕様書作成・仕様設計を含む）を新規作成または既存仕様へ追記し、spec.md/plan.md/tasks.mdまで生成・更新する。要件定義、要件追加/変更、TDD前提の要件整理、仕様の明文化、Spec Kitのspecify/clarify/plan/tasksフロー実行が求められるときに使用。
spec-driven
Spec-driven development workflow. Use when implementing new features, skills, or game mechanics. Ensures specs exist before code.
skill-audit
This skill should be used for periodic review of all Claude Code skills. Triggers include "audit my skills", "which skills need work", "skill inventory", or when starting a skill improvement session. Identifies staleness, gaps, redundancy, and prioritizes improvements.
standards-summary
Your approach to handling standards summary. Use this skill when working on files where standards summary comes into play.
visual-consistency-auditor
Skill for ensuring visual consistency and preventing layout shifts during responsive transitions.
app-dev-workflow
앱 개발 워크플로우를 시작합니다. 요구사항 분석(prd.md) -> 작업 계획(todo.md) -> Agent 분담 실행 -> 코드 리뷰 -> 최종 테스트 순서로 체계적인 앱 개발을 진행합니다. "/app-dev-workflow", "앱 개발 워크플로우", "앱 워크플로우로" 등의 명령으로 활성화됩니다.
dispatching-parallel-agents
並列エージェント派遣スキル。独立した問題に複数エージェントを同時割り当てする方法。
project-manager
Expert project management covering planning, execution, stakeholder management, risk mitigation, and delivery excellence.
project-memory-store
Store project-specific insights and context into file-based memory. Use after completing tasks that reveal important details about THIS codebase. Use when user says "--project-store" or "--learn" (you decide which scope, may use both) or after discovering project-specific patterns. Skip for universal patterns (use coder-memory-store) or routine work.
