Total 30,580 skills, Project Management has 1150 skills
Showing 12 of 1150 skills
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Use before launches, major decisions, or risky initiatives to surface hidden risks.
Guide teams and individuals through setting Objectives, Key Results (OKRs), and annual goals that translate strategy into measurable execution. Use when planning quarterly or annual cycles, setting individual or team goals, aligning on priorities, creating OKRs, writing SMART goals with FROM-TO metrics, reviewing goal cascades, or when the user asks about objectives, key results, goal setting, or planning frameworks. Do not use for purely operational SLA-driven work (use KPIs instead), uncertainty-heavy research (use Discovery OKRs), or reviewing past performance (use a check-in/feedback skill).
Expert in Jira operations using Atlassian MCP - automatically detects workspace Jira configuration or prompts for project details. Use for searching, creating, updating issues, managing status transitions, and handling tasks.
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.
Create a Technical Design Document for your MVP. Use when the user wants to plan architecture, choose tech stack, or says "plan technical design", "choose tech stack", or "how should I build this".
Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project".
Best practices for organizing project folders, file naming conventions, and directory structure standards for research and development projects
CREATE/REPLAN Epics from scope (3-7 Epics). Batch Preview + Auto-extraction. Decompose-First Pattern. Auto-discovers team ID.
Updates ALL task types (implementation/refactoring/test). Compares IDEAL plan vs existing tasks, categorizes KEEP/UPDATE/OBSOLETE/CREATE, applies changes in Linear and kanban.