Total 52,836 skills, Project Management has 1925 skills
Showing 12 of 1925 skills
Use to plan rollout communications, trainings, and assets after pricing changes.
Use to coordinate approvals, communications, and accountability across teams for feedback programs.
Senior Project Manager for Software, SaaS, and digital web/mobile applications. Use for strategic planning, portfolio management, stakeholder alignment, risk management, roadmap development, budget oversight, cross-functional team leadership, and executive reporting for software products.
Use when an agent needs to write user stories for a project
"What is important is seldom urgent and what is urgent is seldom important." Master Dwight D. Eisenhower's prioritization framework to focus on what truly matters. Use when: **Feeling overwhelmed** by too many tasks and not enough time; **Weekly planning** to set priorities for the week ahead; **Daily triage** when everything seems urgent; **Delegation decisions** to identify what others should handle; **Saying no** by recognizing tasks that shouldn't be done at all
Workflow for executing implementation tasks. Use this skill when you need to: (1) Execute a prepared implementation plan (2) Implement tasks sequentially based on dependency resolution (3) For each task: implement → verify → self-review → external review This skill enforces: (a) dependency-based task execution, (b) per-task review cycle.
Structure high-stakes communication with the Pyramid Principle. Use when preparing executive summaries, recommendations, decision memos, or storyline-driven updates that need a clear answer-first flow and defensible support.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
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.
GitHub Project health dashboard. Shows workflow distribution, component health, team workload, items needing attention, and available views.
Use when creating durable work items, managing todo lifecycle, or tracking findings across sessions in the file-based todo system
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. Part of the skills-for-java project