Loading...
Loading...
Found 143 Skills
Use before committing to a task. Provides complexity analysis and scope assessment. Invoke when user asks "how complex" or before large features.
Track management methodology - creating and managing logical work units (features, bugs, refactors) through specification, planning, and implementation phases.
Create comprehensive implementation plans and write them to plan files. Use when the user asks for a plan, comprehensive plan, systematic workflow design, or wants decisions documented in a plan file.
Plan Plus — Brainstorming-Enhanced PDCA Planning. Combines intent discovery from brainstorming methodology with bkit PDCA's structured planning. Produces higher-quality Plan documents by exploring user intent, comparing alternatives, and applying YAGNI review before document generation. Use proactively when user mentions planning with brainstorming, intent discovery, exploring alternatives, or wants a more thorough planning process. Triggers: plan-plus, plan plus, brainstorming plan, enhanced plan, deep plan, 플랜 플러스, 브레인스토밍, 기획, 의도 탐색, 대안 탐색, プランプラス, ブレインストーミング, 企画, 意図探索, 计划加强, 头脑风暴, 深度规划, 意图探索, plan mejorado, lluvia de ideas, planificación profunda, plan amélioré, remue-méninges, planification approfondie, erweiterter Plan, Brainstorming, vertiefte Planung, piano migliorato, brainstorming, pianificazione approfondita Do NOT use for: simple tasks that don't need planning, code-only changes.
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
View a plan's tasks and progress, regardless of output format.
Use Beads (bd tool) for dependency-aware task tracking and long-horizon planning in coding projects. This skill should be used when working on complex multi-step projects that span multiple agent sessions, when discovering new work during implementation, or when explicit task dependency management would improve workflow organization and prevent context loss between sessions.
Create implementation plans with tasks grouped by subsystem. Related tasks share agent context; groups parallelize across subsystems.
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.
Break down complex tasks into atomic, actionable goals with clear dependencies and success criteria. Use this skill when you need to plan multi-step projects, coordinate agents, or decompose complex user requests into manageable sub-tasks.
ISD 연구계획서 통합 입력 템플릿 - Orchestrator용 입력 양식
Use this for complex project planning, full-stack feature implementation, or coordinating multiple skills (Design, Backend, Frontend, Ops) into a cohesive workflow.