session-docs
Load when closing beads tasks, ending significant sessions, or when planning discussions need to be captured
Load when closing beads tasks, ending significant sessions, or when planning discussions need to be captured
GitHub 태스크 이슈카드 기반 구현 완료 리뷰. Use when: (1) PR 전 태스크카드 검토, (2) "리뷰해줘" 요청, (3) Acceptance Criteria 충족 확인, (4) Draft→일반 이슈 전환 확인, (5) 브랜치명 규칙 준수 확인.
Use after writing-plans to decompose monolithic plan into individual task files and identify tasks that can run in parallel (up to 2 subagents simultaneously)
Full workshop for story discovery, user journey mapping, and backlog creation (project)
Master team coordination with leadership, communication, conflict resolution, and collaboration techniques for high-performing teams.
Use this when receiving a change request between the <idea> or <ideas> tags before proposing any changes - 6 point framewor for considering proposed changes (research, confidence gating, intent decomposition, tree of thought alternatives, other angles and refutations) that ensures careful consideration of the impacts and alternatives before attempting changes.
Prioritize tasks and issues to determine what to work on and in what order. Use after identification, when planning work, or when unsure what to do next. This is the third system in the 5-system framework.
Sprint(Iteration) 종료 및 회고 정리. Use when (1) Sprint 마감, (2) 회고 작성, (3) /SEMO:sprint close 커맨드.
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles. Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls.
Bug tracking system using Redis for bCommGuard - find, fix, and mark bugs reported with
Create a short summary of recent handoff log entries without modifying the append-only log.
Create work breakdown structure, resource planning, risk management, quality/testing planning, security/compliance planning, DevOps/CI/CD planning, and Sprint 0 setup.
In scaling companies, once you master a role you must hand it off and move to a bigger, messier challenge. Holding on buries you; giving away allows you to tackle bigger challenges.
Complete strategic problem-solving methodology from "Cracked It!" by Garrette, Phelps & Sibony. Use when users need to solve complex ill-defined business problems, structure and analyze strategic issues, develop and validate solutions, or present recommendations persuasively. Covers the complete 4S Method (State, Structure, Solve, Sell) from problem definition through solution delivery. Use for strategy consulting, business analysis, decision-making, and solving wicked problems that resist simple frameworks.
Generate comprehensive lab member rosters in both markdown and CSV formats. Analyzes member profiles, git history, and alumni information to create detailed rosters with role transitions, team assignments, and career tracking. Use when user mentions roster, team list, lab members, or updating member information.
Use for implementation plans - dispatches fresh subagent per task with quality scoring (0.00-1.00), code review gates, Serena pattern learning, and MCP tracking
タスク依頼時の理解確認システム(5W1H)。playbook 作成前にユーザーの意図を確認し、リスク分析と不明点の洗い出しを行う。pm SubAgent から呼び出される。
Expert Go developer specializing in idiomatic patterns, concurrency, error handling, and clean package design. This skill should be used PROACTIVELY when working on any Go code - implementing features, designing APIs, debugging issues, or reviewing code quality. Use unless a more specific subagent role applies.
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.