Total 43,743 skills, Project Management has 1613 skills
Showing 12 of 1613 skills
Use when running launch command centers, standups, and escalation workflows.
Use to plan rollout communications, trainings, and assets after pricing changes.
Use to set cadences, decision logs, and escalation paths for enterprise pursuits.
Use when coordinating shoots, vendors, budgets, and compliance for video projects.
Operating system for intake, approvals, QA, and training across brand stakeholders.
Guide teams and individuals through setting Objectives, Key Results (OKRs), and annual goals that translate strategy into measurable execution. Use when planning quarterly or annual cycles, setting individual or team goals, aligning on priorities, creating OKRs, writing SMART goals with FROM-TO metrics, reviewing goal cascades, or when the user asks about objectives, key results, goal setting, or planning frameworks. Do not use for purely operational SLA-driven work (use KPIs instead), uncertainty-heavy research (use Discovery OKRs), or reviewing past performance (use a check-in/feedback skill).
Guide for creating and reviewing requirements definitions based on IPA standards. Provides best practices for business analysis, process mapping, data modeling, and review checklists.
Conducts comprehensive requirements review including completeness validation, clarity assessment, consistency checking, testability evaluation, and standards compliance. Produces detailed review reports with findings, gaps, conflicts, and improvement recommendations. Use when reviewing requirements documents (BRD, SRS, user stories), validating acceptance criteria, assessing requirements quality, identifying gaps and conflicts, or ensuring standards compliance (IEEE 830, INVEST criteria). Trigger when users mention "review requirements", "validate requirements", "check requirements quality", "find requirement issues", or "assess BRD/SRS quality".
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
Iterative execution methodology. Small steps, verify each, adapt based on results.
Use when "evaluating technology", "choosing frameworks", "stack comparison", "technology decisions", or asking about "React vs Vue", "PostgreSQL vs MySQL", "AWS vs GCP", "build vs buy"
SPEC workflow orchestration with EARS format, requirement clarification, and Plan-Run-Sync integration for MoAI-ADK development methodology