Total 50,510 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Use jira CLI for Jira operations including issue management, project queries, transitions, and JQL search
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.
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
View a plan's tasks and progress, regardless of output format.
Generate client-friendly monthly invoice summaries by analyzing Git commits and time sheet notes. Synthesizes technical work into business-focused bullet points suitable for client invoicing. Use when preparing monthly billing or project status reports. Triggers on "invoice summary", "monthly billing", "summarize work for client".
Walk through decisions using a 3-part framework (first-principles, cost/benefit, second-order effects). Use when choosing between options, evaluating trade-offs, or making high-stakes decisions.
Apply agile development practices. Use when planning sprints, running ceremonies, or improving team processes. Covers Scrum, Kanban, and agile principles.
Resume work from handoff document with context analysis and validation
Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.
Use this when you need to initialize a new Spec Pack in the AI SDLC workflow of this repository (create a three-digit numbered branch and the `.aisdlc/specs/{num}-{short-name}` directory), or when you are unsure about input parsing, short name rules, UTF-8 BOM file path parameter passing, script invocation methods, or output artifacts when executing `spec-init`.
This skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.