Total 50,510 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
REQUIRED skill for planning and designing coding tasks before implementation. Use this skill when: (1) User asks to "plan", "design", "create a plan", or "think before coding" (2) Complex tasks requiring multiple files or steps (3) Tasks involving both backend and frontend changes (4) Breaking down ambiguous requirements into concrete tasks This skill ensures plans are properly documented, saved as markdown, reviewed by subagent, and registered as todos before any code is written. Do NOT skip this skill for non-trivial tasks.
Use when you have specs or requirements for a multi-step task to break it down into detailed tasks, before executing it
Plan document manager -- create, modify, and organize plan.md with Phase/task structure. 기획서(plan.md) 자동 생성/추가/수정 스킬. Triggers: /plan, "create plan", "기획서", "plan 생성", "Phase 추가"
Status Report Generator - Auto-activating skill for Enterprise Workflows. Triggers on: status report generator, status report generator Part of the Enterprise Workflows skill category.
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components. Use when users need to decompose strategic questions, structure analysis, create work plans, or prepare for case interviews. Apply hypothesis-driven approach to problem-solving.
Use before committing to a task. Provides complexity analysis and scope assessment. Invoke when user asks "how complex" or before large features.
Deterministic plan lifecycle management via scripts/plan-manager.py CLI. Use when user asks to list, show, create, check, complete, or abandon plans, or when session starts and stale plans need surfacing. Use for "check plans", "what's on our plan", "mark task done", "finish this plan", or "create a plan". Do NOT use for executing plan tasks, modifying plan content directly, or performance/refactoring work unrelated to plan tracking.
Technical design interview + adversarial review → living doc Technical Design section ready to implement. Stateful: detects existing sections and resumes where needed. Triggers: 'architect this,' 'how should we build,' 'design the tech,' post-define/design. Not for: scoping (explore), requirements (define), UX (design).
Business case analysis with ROI, NPV, IRR, payback period, and TCO calculations for investment decisions. Use when building financial justification, cost-benefit analysis, build-vs-buy comparisons, or sensitivity analysis.
Archive a completed spec-driven change. Warns on incomplete tasks, moves change to archive/ with a date prefix.
Record a business artifact (.oh/ metis, signal, guardrail, or outcome update). Use when capturing learnings, measurements, constraints, or updating outcome status.
Use when creating durable work items, managing todo lifecycle, or tracking findings across sessions in the file-based todo system