Total 43,811 skills, Project Management has 1613 skills
Showing 12 of 1613 skills
Apply agile development practices. Use when planning sprints, running ceremonies, or improving team processes. Covers Scrum, Kanban, and agile principles.
Use when order-of-magnitude cost estimates are needed to assess financial feasibility, compare cost-effectiveness of alternatives, or identify major cost drivers (not for detailed quotes—that's Procurement)
Convert ambiguous user requests into structured USDM requirements documents. Decomposes requirements into Requirement → Reason → Description → Specification hierarchy. Integrates with GitHub Issues, Asana, and Jira tickets as input sources. Use when: "create requirements", "write requirements document", "USDM", "decompose requirements", "requirements definition", "要件定義", "要件を整理", "要件分解".
Connect to a self-hosted Plane.so instance via API. Use this skill when the user wants to interact with Plane for project management tasks including managing workspaces, projects, work items (issues), cycles, modules, states, and labels.
Brainstorming techniques for idea generation. Use when facilitating brainstorming sessions, leading ideation exercises, or helping teams generate creative solutions.
Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.
Team workflow-oriented planning skill (Phase 2). Before development, refine Jira Story + UI mockups into executable plans and output to docs/plans/{Story-Key}/plan.md
Headcount planning, org design, and team structure optimization. Trigger with "org planning", "headcount plan", "team structure", "reorg", "who should we hire next", or when the user is thinking about team size, reporting structure, or organizational design.
Use when you need to execute I2 (Implementation Execution) in the Spec Pack of sdlc-dev, using `{FEATURE_DIR}/implementation/plan.md` as the sole SSOT to implement in batches, run minimal validation, write back audit information, and report at batch checkpoints; stop immediately when encountering blocks or clarification items.
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth (SSOT) for execution checklist and status), and provide an unambiguous task list for subsequent I2 execution.
Senior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring.
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use when scope is large, requirements are mostly known, and work should be broken into validated phases before execution.