Total 52,553 skills, Project Management has 1920 skills
Showing 12 of 1920 skills
Use when an issue needs deeper analysis than triage — confirming root cause by reading code, verifying file/line references in body are still valid, checking blast radius across the codebase, or proposing a concrete fix direction. One issue per invocation.
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'.
Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.
View and manage workflow states. Use when checking or configuring issue statuses for a team.
You MUST use this when a request needs design decisions before code — new features, product or UX behavior, architecture changes, unclear success criteria, or two materially different approaches. Explicitly specified mechanical refactors, localized fixes with known expected behavior, and single-outcome config changes go straight to implementation.
Run a structured business analysis workflow: requirements elicitation with stakeholder interviews and MoSCoW prioritization, as-is/to-be process mapping with BPMN notation, data-driven analysis (CBA, SWOT, root cause), and production-ready documentation (BRD, FRD, user stories with INVEST acceptance criteria). Triggers on "gather requirements", "write user stories", "map business process", "BRD", "FRD", "gap analysis", "cost-benefit analysis", "facilitate workshop", "business requirements", "process mapping", "as-is to-be", "stakeholder interview", or "business analyst". For management consulting (issue trees, steerCo business cases, operating model), use business-consultant—not business-analyst. For business model canvas, market sizing, and unit economics research, use business-model-researcher. Human data / labeling platform PRDs: product-management-human-data-platform. Monetization PRDs and packaging: product-management-monetization.
This skill should be used when the user asks about enterprise strategy, corporate strategy, business unit strategy, portfolio prioritization, strategic roadmap, growth strategy, diversification, operating model, capability map, strategic initiative, enterprise transformation, board strategy, scenario planning, or competitive positioning at enterprise level. Guides corporate and BU strategy, portfolio prioritization, growth and diversification, market positioning, operating model and capabilities, transformation roadmaps, M&A/partnership/divestiture framing (strategy—not legal DD), scenarios, executive alignment, and KPI trees—not product backlog or program RAID (technical-program-manager), financial models only (financial-analyst), contracts (commercial-counsel), cloud or system architecture alone (enterprise-cloud-architect, senior-system-architecture), or consulting workshops without enterprise portfolio scope (business-consultant).
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
Manage Linear issues, projects, and teams
Iterative PDCA cycle for systematic experimentation and continuous improvement
Comprehensive A3 one-page problem analysis with root cause and action plan