development
AllBeads development process. Use when planning features, creating documentation, tracking work with beads, or understanding the documentation system.
AllBeads development process. Use when planning features, creating documentation, tracking work with beads, or understanding the documentation system.
Implement technical plans from thoughts/shared/plans with verification
The agent implements DORA metrics tracking for measuring and improving software delivery performance. Use when establishing engineering metrics, benchmarking teams, or driving DevOps transformation.
软件研发流程协调器,根据项目阶段智能调度专家和VP级智能体协作。用户启动新项目、规划研发流程、或需要跨团队协调时使用。
Agile methodologies, issue tracking, and team collaboration tools
True parallel sub-agent coordination with wave-based execution. Analyzes phase dependencies, groups independent phases into waves for parallel execution, allocates agents based on complexity score. Proven 3.5x speedup for complexity >=0.50. Use when: executing complex projects, need parallel coordination, want to achieve 2-4x speedup.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Master team dynamics, leadership principles, delegation, 1-on-1s, mentoring, and people management for engineering managers
Create comprehensive implementation plans decomposed into atomic tasks with full beads integration (epic → feature → task hierarchy)
Genera MVPs completos desde SPEC.md orquestando todos los agentes especializados
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)
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.