Total 50,320 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
build
Create a structured session handoff document for continuity across sessions. Use when ending a work session, switching contexts, or before a break. Captures decisions, progress, code changes, and next steps so a future session can pick up where you left off without losing context.
Creates and organizes focused planning views from a subset of roadmap tasks. Use when the user wants to build a task graph, analyze dependencies, identify ready or blocked work, or group near-term and future work into a focused planning workspace.
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation
Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, and suggested next actions — helps identify drift, missing contracts, or unpaired semantic blocks.
Manage video production projects including character profiles, project manifests, workflow history, and asset tracking. Use when creating new projects, managing characters, or tracking production state.
[Workflow] Trigger Greenfield Project Init workflow — start a new project from scratch with full inception, implementation, and integration testing.
This skill should be used when the user asks to "create an issue", "file a bug", "create a feature request", "open a GitHub issue", "report a bug", "request a feature", "create a task", "break this into issues", or describes a feature/bug they want tracked in GitHub. Guides interactive issue creation with structured templates, workspace change attachment, and optional autonomous label for the automated pipeline.
Github Issue Creator - Auto-activating skill for Enterprise Workflows. Triggers on: github issue creator, github issue creator Part of the Enterprise Workflows skill category.
Collaboration workflow for GitHub Issue handling. Used when users receive an issue that needs analysis and response. Through the four-step process of "Diagnosis → Qualification → Decision → Response", produce accurate root cause analysis and appropriate user responses from an issue, avoiding misjudgment of problem types or unprofessional responses.
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant incident or success, at a quarterly review of ongoing processes, or before starting a similar project to capture lessons learned.
Maintain project state across MULTIPLE conversations over days/weeks. Track tasks, decisions, blockers, resources. Auto-update when project mentioned. Generate status reports and proactive reminders.