Total 52,935 skills, Project Management has 1929 skills
Showing 12 of 1929 skills
Research and discovery workflow for document deliverables — competitive analyses, architecture comparisons, ADR scaffolding, literature reviews, vendor evaluations. No TDD requirement. Phases: gathering → synthesizing → completed. Triggers: 'discover', 'research', 'explore topic', or discover.
Lightweight workflow for straightforward changes — plan → implement → optional PR. Direct-commit by default; synthesize is opt-in via synthesisPolicy or a runtime request_synthesize event. Use for trivial fixes, config tweaks, single-file changes, or exploratory work that doesn't warrant subagent dispatch or two-stage review. Triggers: 'oneshot', 'quick fix', 'small change', or oneshot.
Interact with ClickUp tasks and documents - get task details, view comments, create and manage tasks, create and edit docs. Use when working with ClickUp task/doc URLs or IDs.
Use this skill when users need to evaluate potential co-founders, assess founder compatibility, design equity splits, or navigate co-founder relationships. Activates for "should I work with this person," "co-founder fit," "equity split," or founding team questions.
Use when facing decisions with multiple legitimate perspectives and inherent tensions. Invoke when stakeholders have competing priorities (growth vs. sustainability, speed vs. quality, innovation vs. risk), need to pressure-test ideas from different angles before committing, exploring tradeoffs between incompatible values, synthesizing conflicting expert opinions into coherent strategy, or surfacing assumptions that single-viewpoint analysis would miss.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Apply strategic frameworks through facilitated workshop dialogue. Use when user selected framework via choose-framework; explicitly requests specific framework; knows which framework to apply; or needs structured guidance. Conducts 30-60 minute workshops guiding step-by-step through framework application. Creates workshop documents in .frameworks-output/ folder.
Kanban methodology including boards, WIP limits, flow metrics, and continuous delivery. Activate for Kanban boards, workflow visualization, and lean project management.
Expert in protecting projects from scope creep. Covers requirement management, stakeholder negotiation, saying no diplomatically, and keeping projects focused. Understands that scope creep kills more projects than technical debt. Use when "scope creep, feature request, can we also, while you're at it, one more thing, requirements changed, scope management, " mentioned.
Agile product management, Scrum practices, and team collaboration for iterative product development.
Project Intake & Charter: transform an ambiguous project request into a clear, structured project foundation for consulting engagements. Use when a project is in the **Initiation** phase or when a PM needs to clarify objectives, scope, stakeholders, assumptions, initial risks and open questions without performing detailed planning or estimations.
Perform a comprehensive session retrospective. Use when user says "retro", "retrospective", "회고", or at the end of a working session.