Total 30,538 skills, Project Management has 1149 skills
Showing 12 of 1149 skills
Convert meeting discussions into clear, actionable notes with tasks, decisions, and follow-ups fo...
Use when planning work (to create items and tasks), when starting implementation (to mark tasks in-progress), when completing work (to mark tasks done), or to check backlog status. Manages .backlogmd/ for features, bugfixes, refactors, and chores.
Clarify requirements before implementing by asking the minimum must-have questions. Use when a request is underspecified or ambiguous, when the user asks to “ask clarifying questions”, or when multiple plausible interpretations exist and you risk doing the wrong work.
Project Intake & Charter: transform an ambiguous project request into a clear, structured project foundation for consulting engagements. Use when a project is in the **Initiation** phase or when a PM needs to clarify objectives, scope, stakeholders, assumptions, initial risks and open questions without performing detailed planning or estimations.
Risk & Change Management (Devil's Advocate): Identify risks, manage issues, and evaluate change requests. Use this skill to proactively detect threats, assess the impact of changes, and protect the project baseline.
Stakeholder Communication (The Diplomat): Prepare context-aware communications (Emails, Updates, Memos) using project data.
Closure & Learning (The Learner): Formalize project closure, capture lessons learned, and generate final reports.
Senior Business Analyst with 10+ years bridging business and technical teams. Use when conducting market research, competitive analysis, gathering requirements, creating business process models, cost-benefit analysis, or validating assumptions with data.
Use when teams need shared direction and decision-making alignment. Invoke when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or setting behavioral standards. Use when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
Use when managing multiple initiatives across time horizons (now/next/later, H1/H2/H3), balancing risk vs return across portfolio, sizing and sequencing bets with dependencies, setting exit/scale criteria for experiments, allocating resources across innovation types (core/adjacent/transformational), or when user mentions portfolio planning, roadmap horizons, betting framework, initiative prioritization, innovation portfolio, or resource allocation across horizons.
Use when stakeholders have conflicting priorities and need alignment, suspect decision blind spots from single perspective, need to pressure-test proposals before presenting, want empathy for different viewpoints (eng vs PM vs legal vs user), building consensus across functions, evaluating tradeoffs with multi-dimensional impact, or when user mentions "what would X think", "stakeholder alignment", "see from their perspective", "blind spots", or "conflicting interests".
Use when planning high-stakes initiatives (migrations, launches, strategic changes) that require clear specifications, proactive risk identification (premortem/register), and measurable success criteria. Invoke when user mentions "plan this migration", "launch strategy", "implementation roadmap", "what could go wrong", "how do we measure success", or when high-impact decisions need comprehensive planning with risk mitigation and instrumentation.