Total 43,440 skills, Project Management has 1598 skills
Showing 12 of 1598 skills
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
Run blameless post-mortems and retrospectives: Pack with brief, timeline, contributing factors, root causes, action tracker, kill criteria, dissemination plan. Use for postmortem, retro, after-action review, lessons learned. NOT for non-review meetings (use running-effective-meetings), shipping process design (use shipping-products), engineering culture (use engineering-culture), or future risk planning (use planning-under-uncertainty). Category: Leadership.
Collaboration workflow for GitHub Issue handling. Used when users receive an issue that needs analysis and response. Through the four-step process of "Diagnosis → Qualification → Decision → Response", produce accurate root cause analysis and appropriate user responses from an issue, avoiding misjudgment of problem types or unprofessional responses.
/em -stress-test — Business Assumption Stress Testing
PRD construction for work planning. Compulsory in PLAN phase. Builds .prd file as frozen dependency graph of every possible work item before execution begins. Triggers on any new task, multi-step work, or when gm enters PLAN state.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Scrum Master (River). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlo...
Conduct a comprehensive SWOT analysis to audit organizational position. Use when assessing strategic fit, evaluating competitive position, or informing strategic direction.
Implement a full-stack feature following an approved plan. Builds database layer, backend API, frontend components, and tests. Use after plan-feature has produced an approved implementation plan, or when you have a clear set of tasks to implement across the stack.
Requirements Analysis SKILL, which can further interact with users to clarify requirements
Use when renaming a spec plan and updating all references. Triggers on: "rename plan", "change plan name", "plan name is wrong", "update plan name", "fix plan name", "spec rename". Proactively suggest when a plan name is a typo or no longer reflects scope.
Use when modifying an existing em plan or task files. Triggers on: "update em", "change plan", "modify epic", "add task", "remove task", "rename phase", "apply annotations", "edit plan". Applies inline > and >> annotations or accepts conversational changes to plan.md or task milestone files.