[Story]: PM Buddy — onboarding content

[LinseCed]

User Story

As a PM in the buddy's team mode, I want to adjust my members' onboarding paths, review their skip requests and feedback, and write orientation packets for starter tasks — so the onboarding content fits the people on my project. Nothing changes until I confirm it.

Context & Motivation

• Type: Functional (agent actions on the PM surface)
• Parent epic: 05 EPIC - Agent Orchestration & Workflow Actions #54 (05 EPIC – Agent Orchestration & Workflow Actions)
• Teams: team:backend
• Concept: pm-buddy-concept.md
• Builds on: [Story]: PM Buddy — run a managed project from the buddy #312 (team mode, stored proposals, mounting by area); orientation packets reuse the starter-work project resolver from [Story]: PM Buddy — run a managed project from the buddy #312's second backend sub-task

The critical piece of this story: an onboarding path belongs to a person, not a project — one path per user. A change is allowed when the person is on the managed project, and when they are also on another project the PM is told the change applies there too. The path services load elements by id without an owner check, so every element is traced back to its owner before and at confirm.

In Scope

• A member's path: phases, steps, tasks, resources, phase checks; resetting a path
• Skip requests: accept, deny with a comment, delete
• Feedback: read and mark as read
• Orientation packets: view, write, revert to the AI version

Acceptance Criteria

• A manager can change the path of a member of their project, and nobody else's
• A change to a member who is on several projects says so before confirming
• Team mode never marks a hire's task finished or a step started/completed
• Skips and feedback are limited to members of the project
• Orientation packets are limited to tasks whose source belongs to the project
• Every change is a proposal until confirmed; deletes and resets are marked destructive

Technical Notes

• Competency modules and the competency graph are not part of this: competencies have no project.
• No frontend or AI work: tool labels fall back to a generic label, and the persona only describes mounted tools.

Sub-Tasks (by team)

• Backend — team-mode actions for onboarding paths, skips, feedback and orientation packets (Team-mode actions: onboarding paths, skips, feedback and orientation packets sprintstart-backend#228)