Total 53,878 skills, Project Management has 1958 skills
Showing 12 of 1958 skills
Set parent-child task relationship (subtask)
Recommend the next roadmap-backed change, then after explicit confirmation scaffold it as a normal spec-driven change.
Resume work from previous session with full context restoration
Apply Smith and Lewis's paradox theory to identify and manage organizational tensions across performing, organizing, belonging, and learning dimensions. Use this skill when the user needs to diagnose persistent either/or tensions, design dynamic equilibrium strategies that embrace both poles, or when they ask 'why does solving this problem make it worse', 'how do we pursue exploration AND exploitation simultaneously', or 'why do our strategic tensions keep recurring despite resolution attempts'.
Conduct stakeholder analysis using identification, Power-Interest matrix classification, and influence strategy development. Use this skill when the user needs to map stakeholders for a project, manage conflicting interests, prioritize communication, or build a stakeholder engagement plan — even if they say 'who needs to approve this', 'how do I get buy-in', or 'who might block this project'.
Apply Transaction Cost Economics (Williamson, 1975, 1985) to analyze governance structure choices — market, hybrid, or hierarchy — based on transaction characteristics. Use this skill when the user needs to decide make-or-buy, evaluate outsourcing vs vertical integration, design governance mechanisms for inter-firm relationships, or when they ask 'should we build this in-house or outsource', 'why do firms vertically integrate', or 'how should we structure this partnership'.
Use when new insights change the scope, acceptance criteria, domain language, or technical constraints of an existing Epic, Feature, or Task — for example "refine epic
Manage Linear tickets, projects, milestones, and documents. Use for coordinating work across skills (orca-security, multi-repo) or tracking remediation progress.
Append-only task record convention for Loom. Use when reading or writing per-task records under `.agents/tasks/<task-id>/`, when another skill needs to log a lifecycle milestone (saved, decision, readiness, blocker, done), when the user asks about an existing task's status or progress, or when checking task records for drift via the linter. Do NOT trigger for creating new tasks (that is `task-brief`'s job), for general docs/planning unrelated to a task directory, or for historical questions about the retired `task-state-management` system.
Kanban / task board with columns (To do / In progress / In review / Done), draggable-looking cards, assignee avatars, swimlanes, and a top filter bar. Use when the brief mentions "kanban", "task board", "sprint board", "trello", "看板".
You are **SeniorProjectManager**, a senior PM specialist who converts site specifications into actionable development tasks. You have persistent memory and learn from each project.
Turn work into realistic delivery plans and status tracking. USE when breaking projects into executable tasks, managing dependencies, or coordinating cross-functional delivery.