Total 52,120 skills, Project Management has 1902 skills
Showing 12 of 1902 skills
Break one active project into independent, ready-to-claim tasks when probe next routes create_tasks.
Helps engineering managers diagnose team skill gaps and make better hiring and assignment decisions — produces the Dungeon Party archetype model (Warrior, Tank, Healer, Wizard, Rogue), the Barrels and Ammunition framework for understanding throughput limits, the Commandos/Infantry/Police phase model, and a minimum team size guideline. Use when the user says "team balance," "what roles do I need," "who should I hire next," "team is missing something," "skill gaps," "team is slow despite headcount," "this person thrived before but struggles now," or "what type of engineer should I hire."
/cs:post-mortem <decision> — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop.
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
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.
Generate concise initiative summaries from One Horizon initiative data. Use when asked "summarize these initiatives", "give me initiative status", or "prepare initiative update notes". Requires One Horizon MCP.
Scrum master for sprint planning and story preparation. Use when the user asks to talk to Bob or requests the scrum master.
Retrieve ALL information from a Jira ticket (description, comments, subtasks, attachments metadata, labels, sprint, status, assignee, reporter, linked issues, custom fields, acceptance criteria) and persist it as a single Markdown file. Use whenever the user says "fetch ticket", "retrieve Jira", "pull ticket info", "get ticket details", "look up ticket", "grab the Jira", "what does ticket X say", "check the ticket", "read the ticket", "show me the ticket", or provides a Jira ticket URL or key like PROJECT-1234. Also triggered by the orchestrating-jira-workflow skill as Phase 1 of the end-to-end pipeline. Trigger even if the user only pastes a ticket key with no other context — that alone means "fetch this ticket." This skill ONLY retrieves — it never modifies the ticket or starts implementation.
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.
Hive integration. Manage Users, Projects, Actions, Notes, Files, Activities and more. Use when the user wants to interact with Hive data.
Apply principled negotiation using BATNA, ZOPA, and the Harvard method to prepare for and conduct negotiations. Use this skill when the user needs to prepare for a negotiation, evaluate their bargaining position, design win-win solutions, or handle difficult negotiation situations — even if they say 'how do I negotiate this deal', 'what's my leverage', 'they won't budge on price', or 'help me prepare for this meeting'.
Apply Agency Theory (Jensen and Meckling, 1976) to diagnose principal-agent problems — moral hazard, adverse selection — and design governance mechanisms to align interests. Use this skill when the user needs to analyze conflicts of interest between owners and managers, design incentive or monitoring structures, evaluate corporate governance effectiveness, or when they ask 'how do we ensure managers act in shareholders interest', 'why is this incentive plan failing', or 'what governance mechanisms reduce agency costs'.