hamburger-method
Applies the Hamburger Method to slice features into vertical deliverable pieces. Use when user asks how to slice work, break down features into layers, or wants to deliver incrementally. Helps generate 4-5 options per layer and compose minimal vertical slices. Use when: - Feature feels large but not obviously splittable with story-splitting heuristics - User asks "how to slice" or "how to deliver incrementally" - Need to generate multiple implementation options - Want to compose end-to-end vertical slices Do NOT use when: - Story has obvious "and", "or", "manage" indicators (use story-splitting instead) - User is asking HOW to implement (use micro-steps-coach instead) - Feature is already small (< 1 day work)
work-intake
Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.
secondbrain-adr
This skill should be used when the user asks to "create ADR", "document decision", "architecture decision", "add decision record", or mentions needing to record a technical decision with status tracking and category organization.
plan-executor
계획 수립 및 자동 플래닝 워크플로우 실행. "계획", "계획 세워줘", "플래닝", "plan", "구현 계획", "계획 먼저", "분석하고 구현", "설계", "워크플로우" 키워드로 활성화. 병렬 탐색 에이전트로 코드베이스 분석, 다중 관점 계획 수립, 의존성 기반 병렬 실행 지원. 복잡한 작업의 구조화된 계획이 필요할 때 사용. (계획, 플래닝, plan, 구현 계획, 설계, 워크플로우, 분석 후 구현)
reaching-consensus
Facilitate group decision-making. Use when teams need to align on decisions, resolve disagreements, or make collective choices. Covers consensus techniques.
skeleton-of-thought
INVOKE for planning and outlining before implementation. Produces visible skeleton then expansion. Use before implementing features or creating structured documents. Triggers: planning, outlining, structuring approaches, roadmaps, breaking into phases.
handoff
Create a structured session handoff document for continuity across sessions. Use when ending a work session, switching contexts, or before a break. Captures decisions, progress, code changes, and next steps so a future session can pick up where you left off without losing context.
devexec-plan
This skill should be used for development tasks that require detailed technical planning with persistent documentation. Use when the task involves architectural decisions, multi-phase implementation, external dependencies, or when the user explicitly requests an execution plan.
event-storming
Event Stormingでイベント（動詞の過去形）を中心に、コマンド・集約・リードモデルを抽出/命名/レビューする作業に使う
policyengine-period-patterns
PolicyEngine period handling - converting between YEAR, MONTH definition periods and testing patterns
analysis-swarm
Multi-persona analytical framework for comprehensive code review and decision-making
task-sorting
Provides stable task list sorting across four dimensions (Priority, Due Date, Created Date, Alphabetical) with ascending/descending toggles, tie-breaking rules, and visual sort indicators. Default sort prioritizes VERY IMPORTANT tasks first, then by soonest due date.
background-planner
백그라운드에서 여러 에이전트가 병렬로 기획을 수행하고 결과를 자동 저장합니다. 세션이 컨텍스트 제한에 도달해도 에이전트들은 계속 실행됩니다. "백그라운드 기획", "bg plan", "병렬 기획" 요청 시 활성화됩니다.
work-breakdown
Break down features and requirements into actionable, implementable tasks with clear scope and acceptance criteria
decomposing-tasks
Break down large tasks into smaller, actionable items. Use when planning sprints, estimating work, or creating implementation plans. Covers task breakdown strategies.
agentuity-cli-project-show
Show project detail. Requires authentication. Use for project management operations
micro-steps-coach
Breaks down ANY work into 1-3 hour micro-steps with zero downtime. Use for large refactorings, technical improvements, debugging, research, migrations, or any work that feels too big or risky. Automatically applies expand-contract pattern for risky changes. Forces smallest safe increments for all work types. Use when: - Work feels too big or risky (refactoring, migrations, performance fixes) - Database schema changes, API changes, service replacements - User asks "how do I implement" after deciding what to build - Work will take more than 1 day Do NOT use when: - User is still deciding WHAT to build (use story-splitting or hamburger-method first) - Work is already small (< 3 hours) - User asks for architectural review (use complexity-review instead)
adversarial-review
Implements Adversarial Agile Processes (AAP) for document and code review. Challenges assumptions, questions decisions, and suggests improvements. Use when reviewing PRs, documentation, or architectural decisions.
capacity-planning
Plan infrastructure capacity for expected load. Use when sizing systems, planning for growth, or analyzing resource requirements. Covers load estimation and resource sizing.
