Total 50,320 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Audit which product development lifecycle phases have skills and which have gaps when the user asks to check skill coverage, audit skills, or find lifecycle gaps
Create or update project charters from interactive or provided principle inputs, ensuring all dependent templates remain synchronized. Applicable to project management, specification formulation, charter maintenance, and team collaboration scenarios. Trigger words include "speckit constitution", "create charter", "update charter", "project charter", "formulate specification", "team charter"
Know the boundaries of your expertise and operate within them. Use when evaluating opportunities, making decisions outside your domain, or assessing when to defer to experts.
Use this skill when facilitating remote team collaboration - async-first workflows, documentation-driven decision making, meeting facilitation, and distributed team communication. Triggers on designing async processes, writing RFCs or decision docs, preparing meeting agendas, running standups or retros, establishing communication norms, reducing meeting load, or improving handoff quality across time zones.
Use this skill when designing OKR systems, writing performance reviews, running calibration sessions, creating PIPs, or building career ladders. Triggers on OKRs, performance reviews, calibration, PIPs, career ladders, leveling frameworks, feedback cycles, and any task requiring performance management system design.
Run a Virtual Think Tank — a structured multi-persona debate — before planning or making architectural/design/strategic decisions. Use this skill whenever the user is about to plan a system, make a technology choice, evaluate trade-offs, decide on an approach, or faces any decision where multiple perspectives would sharpen the outcome. Also trigger when the user says "think tank", "debate this", "perspectives on", "trade-offs", "should I use X or Y", "help me decide", "before we plan", or asks for pros/cons of competing approaches. This skill should run BEFORE any implementation planning begins — it produces a structured analysis that feeds into better plans.
Requirements Review SKILL, which can further interact with users to clarify requirements
Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.
Use when defining stopping rules for projects, avoiding sunk cost fallacy, setting objective exit criteria, deciding whether to continue/pivot/kill initiatives, or when users mention kill criteria, exit ramps, stopping rules, go/no-go decisions, project termination, sunk costs, or need disciplined decision-making about when to quit.
MeisterTask integration. Manage Projects, Users, Roles. Use when the user wants to interact with MeisterTask data.
This skill should be used when the user wants to identify the single highest-impact improvement to make to their project. Triggers on requests like "what should I build next", "innovate", "best improvement", "next big thing", or when seeking the most compelling addition to a codebase.