Total 54,401 skills, Project Management has 1985 skills
Showing 12 of 1985 skills
Manage project context effectively. Use when onboarding, context switching, or maintaining project knowledge. Covers context capture and sharing.
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
Use when a plan, PRD, or spec has vague requirements, undefined terms, or missing details - conducts structured interview using AskUserQuestion to surface hidden assumptions, challenge ambiguities, and produce implementation-ready specs. Also use proactively when encountering plans that say things like "make it faster" or "improve UX" without concrete definitions.
Collect improvement insights from UI/UX reviews, document research, or external references, convert confirmed items into development requirements. Use when users have optimization suggestions, research findings, or want to improve based on external references. Triggers on keywords like "insights", "improvements", "optimize", "review findings", "research", "reference", "optimization suggestions", "review results", "research".
This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It checks epic parent relationships and validates description completeness for coding assistants, developers, and stakeholders.
Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.
Map what we're optimizing and what constraints we treat as real. Use before jumping to solutions, when hitting repeated blockers, or when patches keep accumulating.
Entrepreneurial Operating System (EOS) based on Gino Wickman's "Traction". Use when you need to: (1) implement a complete business operating system, (2) create Vision/Traction Organizer (V/TO), (3) set quarterly rocks (priorities), (4) run Level 10 meetings, (5) build accountability charts, (6) solve issues using IDS (Identify-Discuss-Solve), (7) align leadership team on vision and execution, (8) get a grip on your business.
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.
Simplified state file management with consolidated FLOW.md (project) and ITEM-XXX.md (per-item) files
Use when coordinating shoots, vendors, budgets, and compliance for video projects.
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.