Total 54,043 skills, Project Management has 1978 skills
Showing 12 of 1978 skills
Trello integration. Manage Boards, Members, Labels. Use when the user wants to interact with Trello data.
/em -board-prep — Board Meeting Preparation
Deep research and discovery before building something new. Explores local projects for reusable code, researches competitors, reads forums and reviews, analyses plugin ecosystems, investigates technical options, and produces a comprehensive research brief. Three depths: focused (30 min), wide (1-2 hours), deep (3-6 hours). Triggers: 'research this', 'deep research', 'discovery', 'explore the space', 'what should I build', 'competitive analysis', 'before I start building', 'research before coding'.
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.
This skill should be used when the user asks about Wardley Mapping, evolution stages, strategic positioning, situational awareness, technology evolution, competitive landscape, creating maps, value chain decomposition, gameplay patterns, doctrine assessment, doctrine maturity, climatic patterns, climate assessment, build vs. buy decisions, inertia analysis, D&D alignment of strategies, peace/war/wonder cycles, play-position matrix, pioneers/settlers/planners, or quantitative evolution scoring including differentiation pressure, commodity leverage, weak signal detection, and readiness scores.
Help identify and evaluate communities to build a minimalist business around. Use when someone is looking for a business idea, trying to find their community, or wondering where to start as an entrepreneur.
Resolve implementation ambiguities before planning begins. Two modes: Discussion mode surfaces gray areas with concrete options for greenfield work. Assumptions mode reads the codebase, forms evidence-based opinions, and asks the user to correct only what's wrong (brownfield work). Use for "discuss ambiguities", "resolve gray areas", "clarify before planning", "assumptions mode", "what are the gray areas", "before we plan". Do NOT use for broad design exploration (use feature-design) or for planning itself (use feature-plan).
Suggest what to work on next based on project state and session context. Considers proximity, momentum, status, and constraints.
Propose a new spec-driven change. Scaffolds proposal.md, design.md, tasks.md, and questions.md for a named change, populated with project context.
List tasks from One Horizon — planned, completed, blocked, initiatives, or bugs. Use when asked "what's on my plate", "what did I ship", "show blockers", "what initiatives are active", "show open bugs", "what should I pick up next", or "what is the team working on". Requires One Horizon MCP.
Discuss and brainstorm a spec-driven change from a rough idea, then propose a change name and, after explicit confirmation, generate the same five proposal artifacts as spec-driven-propose.
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"