Total 52,553 skills, Project Management has 1920 skills
Showing 12 of 1920 skills
Update initiative tasks in One Horizon, including status, ownership, parent linkage, and taxonomy labels. Use when asked to "update initiative status", "reassign initiative", or "move this under another initiative". Requires One Horizon MCP.
Final pass to identify missed items, edge cases, and risks before considering a scope done
Syntax reference for Backlog notation (Backlog記法), the native markup syntax for Nulab Backlog. Covers headings, lists, tables, text styling, links, code blocks, and other formatting elements.
Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.
Captures, enriches, tags, and prioritizes roadmap tasks. Use when the user wants to note work quickly, add missing task details, organize a backlog, or reprioritize an existing list of tasks.
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 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'.