Total 50,315 skills, Project Management has 1842 skills
Showing 12 of 1842 skills
Compares actual spend and revenue against forecasts. Provides variance analysis and corrective insights to ensure financial discipline.
Create PLAN.md file with phase-based breakdown for issues. Use after creating an issue with /issue to break down work into phases.
Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
Transform the most important meeting on your calendar. Master the art of 1:1s that build trust, develop people, and surface problems before they become crises. Use when: **New manager** learning to run effective 1:1s; **Improving existing 1:1s** that feel unproductive; **Building relationships** with new direct reports; **Developing talent** through coaching conversations; **Addressing performance issues** early
Fast decision-making methodology for time-critical situations. Use when you have minutes (not hours) to decide, during incidents, emergencies, or hard deadlines. Optimizes for "good enough now" over "perfect later". Unlike other patterns that maximize quality, RTR maximizes decision speed while maintaining acceptable quality floors.
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.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Task generation skill based on the speckit workflow, used to generate actionable, dependency-ordered tasks.md from available design documents. Use this skill when you need to generate detailed task lists for feature development based on design documents such as spec.md, plan.md, data-model.md, contracts/, etc. Trigger words include "speckit tasks", "generate tasks", "task planning", "feature task decomposition", "create tasks.md", etc.
Execute the implementation planning workflow and generate design artifacts using the plan template. Trigger phrase: "speckit plan".
Converts unstructured field notes, text messages, voice-to-text transcripts, or informal subcontractor updates into a properly formatted Solar EPC construction daily report. Use this skill whenever a user provides raw field notes, a dump of information from a site superintendent, a forwarded text thread, or any informal description of a day's construction activity and needs it turned into a structured daily log. Trigger for phrases like "format this into a daily report", "turn this into a daily log", "my super sent me this", "here's what happened on site today", "write up today's progress", or when a user pastes a block of unstructured text that describes construction activity. Also trigger when a user asks how to document a weather delay, crew idle time, or a site condition that affected production. Every unrecorded day of construction is an unprotected schedule claim.
Create subtasks in Jira from a previously generated task plan. Reads the plan from docs/<TICKET_KEY>-tasks.md and creates one Jira subtask per task under the parent ticket. Use when the user says "create subtasks", "push tasks to Jira", "sync plan to Jira", "create Jira tickets", "make subtasks for PROJECT-1234", or anything about turning a plan into Jira issues. Also triggered by the orchestrating-jira-workflow skill as Phase 4. Requires the task plan to already exist (run planning-jira-tasks first if it does not). Use this skill even if the user just says "push to Jira" or "create the tickets" after a planning phase — those are subtask creation requests.
Use when breaking work into discrete steps, tracking progress through multi-step implementations, or managing implementation task lists. Triggers when an approved plan needs to be converted into tracked tasks, when progress reporting is needed during execution, or when checkpoint reviews are required between task batches.