Total 54,149 skills, Project Management has 1982 skills
Showing 12 of 1982 skills
Use after planning completes and before any implementation begins. Verifies that the current phase contract, story map, and bead graph are structurally sound, execution-ready, and aligned with locked decisions. Use for prompts like "validate the plan", "is this ready to build?", "check the bead graph", "verify execution readiness", or whenever there is doubt about whether the current phase is safe to execute.
Use when starting a new project from scratch, before any technical decisions, to explore the idea through structured sessions and produce a brainstorming synthesis
Plan and file goals and feature issues through conversation. Use when the user wants to create goals, plan features, file issues, or discuss what to build next.
Time-boxed technical investigation with structured output. Use for feasibility studies, architecture exploration, integration assessment, performance analysis, or risk evaluation. Creates spike tasks in ohno, enforces time-boxing, generates spike reports, and creates actionable follow-up tasks.
Create context handoff when pausing work mid-phase
Apply structured problem-solving using MECE principle, issue trees, hypothesis-driven approach, and the Pyramid Principle. Use this skill when the user faces a complex, ambiguous problem and needs to decompose it systematically, structure a consulting-style analysis, or organize recommendations clearly — even if they say 'where do I start', 'this problem is too big', 'help me break this down', or 'structure my thinking'.
Pre-mortem risk analysis expert that classifies risks as Tigers, Paper Tigers, and Elephants to surface launch-blocking issues before they happen.
Onboarding guide for new team members in the agile flow with AI. Use when someone new joins the team and needs to understand how the planning, execution, and tracking flow works with AI agents.
Enter this sub-process when developing new features — turn the vague idea of "adding X capability" into a closed-loop acceptance process, with solution files archived so that both AI and users can later check what was thought and why decisions were made at that time. Trigger scenarios are focused on new capabilities ("develop new features", "add X", "implement XX") and do not address bugs in existing code. This skill only handles routing, deciding which next step to take among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack. Use this skill whenever someone wants to understand where they're spending their management energy, find blind spots, get a monthly self-reflection on their EM focus, or hear phrases like "score my EM grid", "where am I spending time as a manager", "what are my blind spots", "analyze my calendar as EM", "which EM areas am I neglecting", "how balanced is my management focus", or "check my EM grid coverage". Always pull live calendar data — never ask the user to describe their week manually.
Validate plans against 10 verification dimensions before execution begins. Uses goal-backward analysis to catch dropped requirements, vague tasks, missing dependencies, and scope overreach. Produces PASS/BLOCK verdict with structured findings. Use for "check plan", "validate plan", "is this plan ready", "review plan before executing", or "/plan-checker". Do NOT use for plan creation (use feature-plan or workflow-orchestrator) or plan lifecycle management (use plan-manager).
Create detailed, phased implementation plans through interactive research and iteration. Use when the user explicitly asks to "create a plan", "plan the implementation", or "design an approach" for a feature, refactor, or bug fix. Do not use for quick questions or simple tasks.