Use this skill when the user says "project manager", "pm", "where are we", "what's in progress", "what should I work on next", "let's work on this project", "project status", "open issues", "what's next", or asks about Linear issues, GitHub PRs, or issue tracking for the current project. Also use proactively when the user describes work that doesn't appear to be tracked in Linear, when starting new work on main/master, or when branch naming suggests untracked work.
From project-managernpx claudepluginhub nthplusio/functional-claude --plugin project-managerThis skill uses the workspace's default tool permissions.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Central routing skill for project management workflows. Delegates to focused skills based on the task.
| Task | Skill to use |
|---|---|
| Session briefing, what's in progress, what's next | pm-status |
| Create, update, or close a Linear issue | pm-issues |
| Create a branch or write a PR description | pm-branches |
| Changing direction mid-feature, pivoting | pm-pivot |
The pm-session-start hook has already injected the active project context into this session. Refer to the Active Project section at the top of the system context for:
At the start of any Linear-related operation, verify the MCP is available:
Use the Linear MCP (e.g., get_user { query: "me" } or list_teams) to confirm it responds.
If it fails:
~/.claude/project-manager/cache/<slug>/context.json for last-known issue stateWhen the user describes work they're about to do, check whether it maps to an open Linear issue. If not, proactively suggest:
"I don't see a Linear issue for this. Want me to create one?"
Then use the pm-issues skill to draft it with the appropriate template.
At session start, evaluate the current branch and suggest appropriate actions:
The user is about to work without a feature branch. Before any code changes:
pm-issuespm-branches (e.g., feat/ENG-42-description)"You're on main. Let's identify or create a Linear issue first, then set up a branch."
The branch name doesn't contain a Linear issue ID (e.g., feat/add-auth instead of feat/ENG-42-add-auth):
pm-issues"This branch doesn't have a Linear ID. Is it related to an existing issue?"
The branch contains a Linear ID (e.g., feat/ENG-42-auth-middleware):