Total 54,043 skills, Project Management has 1965 skills
Showing 12 of 1965 skills
Business analysis expert who drives project discovery, market research, and requirements validation within the BMAD methodology
Sync project state with Linear — detect gaps, consolidate objectives, clean up, route to next action
Use when writing specifications for features, projects, or requirements — applies Jobs to Be Done (JTBD) methodology with acceptance criteria focus, no implementation details, and SLC release planning
Spec-driven development workflow manager. Use when: (1) creating a DRAFT spec from input files or raw ideas, (2) creating a chunk plan from a DRAFT spec, (3) implementing a DRAFT spec (DRAFT to IMPLEMENTED transition), or (4) managing spec state transitions. Triggers on "create spec", "draft spec", "implement spec", "chunk plan", "spec workflow", or references to *-spec.md files.
Trigger: Call this skill when the problem is complex, has multiple conflicting factors, unclear priorities, or you don't know what to solve first; common signals include trade-off, bottleneck, unknown root cause, unclear priority order, and mutual restraint between multiple problems. Trigger when a problem contains competing forces, unclear priorities, or no obvious entry point. Use this skill to identify contradictions, isolate the principal contradiction, classify its nature, and choose the right response.
Triggers only when the user wants to do spec coding.
Create phases to close all gaps identified by milestone audit
Apply organizational ambidexterity theory to balance exploration and exploitation activities. Use this skill when the user needs to diagnose whether an organization is over-exploiting or over-exploring, design structures that support both innovation and efficiency, or evaluate the tension between short-term performance and long-term renewal.
Apply Weick's sensemaking theory to analyze how individuals and organizations construct meaning from ambiguous situations. Use this skill when the user needs to analyze organizational responses to crises, understand how interpretive frames shape action, diagnose breakdowns in collective understanding, or when they ask 'how did they interpret this situation', 'why did the organization fail to see the warning signs', or 'how do people make sense of disruption'.
Create structured meeting minutes with decisions, action items, and follow-up tracking. Use this skill when the user needs to document meetings effectively, track action items, improve meeting productivity, or set up a meeting note system — even if they say 'take notes for this meeting', 'what was decided', 'who's responsible for what', or 'our meetings have no follow-through'.
This skill should be used when a user wants to create, draft, or plan a GitHub Epic issue — for example "write an epic", "I want to define a new initiative", "scope out this strategic project", "turn this idea into an epic", "plan work that spans multiple features", or "start from a bounded context". Also use when the user asks to define domain outcomes, capture a large initiative before breaking it into features, or describe work in terms of business goals rather than technical tasks.
Stop being a "nice" manager. Learn Kim Scott's framework for caring personally while challenging directly—the combination that builds trust and drives performance. Use when: **Giving feedback** (positive or constructive); **Building trust** with direct reports; **Performance conversations** that need to happen; **Team culture building** for high performance; **New manager development** learning to have hard conversations