Total 50,473 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
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.
Master career development, engineering ladders, IDPs, succession planning, and mentoring for engineering teams
Manage protocol/standard specifications that define what a system must do. Use to create, import, or update the contract that TASKs implement against.
Create PLAN.md file with phase-based breakdown for issues. Use after creating an issue with /issue to break down work into phases.
SPEC workflow orchestration with EARS format, requirement clarification, and Plan-Run-Sync integration for MoAI-ADK development methodology
Technical leadership advisor for CTOs on architecture decisions, engineering strategy, team scaling, technical debt management, and technology evaluation.
Workplace health and wellness expertise for employee wellness programs, mental health initiatives, ergonomics and safety, healthcare benefits strategy, and health analytics. Use when designing wellness programs, improving workplace safety, or analyzing health metrics.
Evaluates whether a business idea is technically buildable and financially viable. Covers unit economics (CAC, LTV), revenue modeling, break-even, and go/no-go verdicts. Triggers on: "feasibility assessment", "viability analysis", "unit economics", "build vs buy", "go/no-go decision", "ROI projection".
Resolve a conflict between two functional specs in a ***plain spec file. Use when conformance tests for a previously passing spec start failing after a new spec is rendered, or when a potential conflict is detected while adding a new functional spec (via `add-functional-spec` or `add-functional-specs`).
Review an implementation against task file requirements. Checks every spec scenario and Done When criterion, identifies gaps, and reports them. Use when the user says "task compliance", "check compliance", "review against the task", or to verify implementation completeness before shipping.
Drives interactive requirement discovery to produce spec files. Use when the user says "spec this", "write specs", "create specs", or "run the spec skill".
Conducts retrospective with learnings and improvement actions. Use when a cycle, sprint, or delivery has ended and the team needs to reflect on what worked and what needs to change. Also absorbs post-implementation reflection aspects.