Use this skill when the user changes direction mid-feature, describes a significant scope change, says the approach isn't working, wants to abandon the current approach, or says "we need to rethink this", "let's change direction", "this isn't right", "pivot", "different approach". Also use when the user's current work no longer matches the active Linear issue.
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.
When work diverges from the original Linear issue, surface the decision clearly and recommend a path.
A pivot has occurred when ANY of these are true:
Clearly state what changed:
"The current approach differs from ENG-42 (Auth middleware refactor). Originally we were planning [original approach], but now we're [new approach]."
Evaluate and recommend ONE of these options — don't just list them, pick the most appropriate one and explain why:
When to recommend: The core goal is the same, only the implementation approach changed.
When to recommend: The scope, goal, or acceptance criteria fundamentally changed.
<type>/<NEW-ID>-<description>When to recommend: The pivot revealed additional work that should be tracked separately.
After the user confirms:
For Option A — Update existing:
save_issue { id: "<issue_id>", description: "<updated>", title: "<updated if needed>" }
For Option B — New issue + cancel old:
save_issue { team: "<team_key>", title: "...", description: "..." } // new issue
save_issue { id: "<old_id>", state: "cancelled" }
To find the cancelled state name: list_issue_statuses { team: "<team_key>" }
Then use pm-branches to create a new branch with the new issue ID.
For Option C — Split:
save_issue { team: "<team_key>", title: "...", description: "..." } // new direction
save_issue { id: "<old_id>", description: "<narrowed scope>" }
Write the updated issue context to ~/.claude/project-manager/cache/<slug>/context.json.