Total 30,584 skills, Project Management has 1151 skills
Showing 12 of 1151 skills
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Decompose high-level objectives into atomic implementation tasks for Python/React projects. Use when breaking down large features, multi-file changes, or tasks requiring more than 3 steps. Produces independently-verifiable tasks with done-conditions, file paths, complexity estimates, and explicit ordering. Creates persistent task files (task_plan.md, progress.md) to track state across context windows. Does NOT cover high-level planning (use project-planner) or architecture decisions (use system-architecture).
Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
Task Planning Specification, applicable to complex tasks (≥3 steps), including requirement decision-making and project plan creation. It covers planning specifications, requirement decision-making processes, and project plan generation tools.
Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.
Conducts comprehensive requirements review including completeness validation, clarity assessment, consistency checking, testability evaluation, and standards compliance. Produces detailed review reports with findings, gaps, conflicts, and improvement recommendations. Use when reviewing requirements documents (BRD, SRS, user stories), validating acceptance criteria, assessing requirements quality, identifying gaps and conflicts, or ensuring standards compliance (IEEE 830, INVEST criteria). Trigger when users mention "review requirements", "validate requirements", "check requirements quality", "find requirement issues", or "assess BRD/SRS quality".
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.
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.