dannys-claude

Add backlog items to an existing sprint through guided brainstorming and planning. Automatically detects sprint context or asks for sprint location. Includes brainstorming phase, plan mode for task design, and ensures tasks are sized for single Claude Code sessions. Triggers include "add backlog", "new feature", "add task", "백로그 추가", "기능 추가", "태스크 추가".

Initialize a sprint with kanban-style structure for multi-agent collaboration. Use when user wants to start a sprint, set up sprint structure, or manage work with multiple agents. Triggers include "new sprint", "init sprint", "setup sprint", "start sprint", "스프린트 시작", "스프린트 초기화", "새 스프린트". Creates BACKLOG.md, HANDOFF.md, INSTRUCTION.md, and sets up active/, refs/designs/, refs/plans/ folders.

Design Feature or Task in detail within a sprint. Refines backlog items through brainstorming, creates implementation plan in Plan mode, and adds Sub-tasks to BACKLOG.md upon approval. Triggers: 'plan task', 'plan feature', 'plan backlog'

Review completed Task or Feature deliverables. Uses type-specific checklists (coding/docs/ideation/general) for quality review. Two modes: default (creates improvement Tasks) and immediate-fix (fixes issues directly). Triggers: 'review task', 'review feature', 'review backlog'

Review work in the current session after an agent marks a task as review. Applies type-specific criteria (coding/design/docs/general), reports findings, user selects improvements, enters Plan Mode, then executes improvements and marks task done. Triggers: 'review work', '작업 리뷰', '리뷰해줘'

Apply latest sprint-init template changes to existing sprints. Updates only rules/guidelines sections while preserving user data (Features, Tasks, tables). Triggers: 'update sprint', 'upgrade sprint', 'update template', 'update sprint version'

Automatically execute all Tasks in a Feature. Creates an Agent Team with Worker/Verifier teammates, enables bidirectional communication via SendMessage, and handles Review & Refactor. Triggers: 'work on feature', 'feature 진행', 'feature 실행', '피처 진행', 'run feature'

Explain any subject — architecture, technical concepts, decision options, project progress, business domains — using storytelling, diagrams, and examples. Always starts with a high-level overview, then explores multiple facets. Triggers: 'explain', '설명해줘', '알려줘', '이해하고 싶어', '뭐야', '어떻게 동작해'

Use when recording an architecture decision as an ADR. Triggers: 'cai-add-decision', 'decision 기록', 'ADR 추가', 'add decision', '결정 기록', '아키텍처 결정'

Use when recording a future plan or direction. Triggers: 'cai-add-roadmap', 'roadmap 추가', '계획 기록', 'add roadmap', '로드맵 추가', '미래 계획'

Use when creating or updating a spec document. Triggers: 'cai-add-spec', 'spec 생성', 'spec 추가', 'spec 업데이트', 'add spec', 'update spec'

Use when setting up CAI for a project. Triggers: 'CAI setup', 'cai-init', 'context initialize', 'CAI 세팅', 'context 초기화'

Use when gathering information from the user through conversational dialogue — onboarding context collection, spec scope clarification, decision rationale gathering. Triggers: 'interview', 'cai-interview'

Use when onboarding a project into CAI. Triggers: 'cai-onboard', 'onboard', '온보딩', 'onboarding', '프로젝트 분석'

Use when upgrading CAI to the latest version. Triggers: 'cai-upgrade', 'context upgrade', 'context 업그레이드', 'update CAI'

A skill that deeply analyzes famous open-source codebases and generates a technical biography-style book. Use when studying the architecture/design philosophy of projects like Doom, Bitcoin, Redis, libuv, PostgreSQL. Trigger on requests such as "analyze ~~", "create a walkthrough for ~~", "write ~~ as an architecture book", "codebase analysis", "project walkthrough", "x-ray", "codebase x-ray". Analysis results are stored in a reusable artifact store for future use without re-analysis.

Use when creating a custom domain agent. Triggers: 'cai-add-agent', 'agent 추가', 'domain agent', 'add agent', '에이전트 추가', '에이전트 생성'

Use when capturing knowledge from current session. Triggers: 'cai-capture-lesson', 'lesson 기록', '교훈 캡처', '배운 것 기록', 'capture lesson', '세션 회고', '레슨 캡처'

Use when checking spec freshness across the project. Triggers: 'cai-drift-check', 'drift 검사', 'stale 체크', 'drift check', '드리프트 검사', '문서 점검', 'spec 점검'