メニュー
Manage sprints, releases, and sprint commitment in P4 Plan. Use when user mentions sprints, sprint planning, capacity, velocity, committing work, iterations, burndown, releases, milestones, versions, or tagging.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Author HTML-formatted comments and multiline field values that render correctly in both the Qt desktop client and the React web client. Use when posting/editing comments, setting Multiline Text custom fields, or writing detailedDescription/stepsToReproduce on a Bug.
Guide custom field management, configuration, and usage in P4 Plan. Use when user mentions custom fields, custom columns, metadata, tags, categories, or project-specific data.
Format @user mentions inside HTML comments and multiline fields so they render as a proper link in both the Qt desktop client and the React web client. Use when the user wants to ping someone, notify a teammate, address @-name, or reference a user inside a comment / description / steps to reproduce.
Manage tasks, status updates, assignments, comments, and attachments in P4 Plan. Use when user mentions tasks, status, updates, assignments, my work, todo list, assign, comments, attachments, or collaboration.
Guide backlog refinement sessions, story refinement, estimation, and prioritization in P4 Plan. Use when user mentions backlog, refinement, estimation, story points, or prioritization.
Guide bug tracking workflows including creation, triage, severity classification, and resolution in P4 Plan QA. Use when user mentions bugs, defects, QA, triage, severity, quality assurance, create bug, or fixing issues.
| name | p4-plan-planning |
| description | Manage sprints, releases, and sprint commitment in P4 Plan. Use when user mentions sprints, sprint planning, capacity, velocity, committing work, iterations, burndown, releases, milestones, versions, or tagging. |
The Planning section contains sprints, scheduled tasks, and releases.
| User Intent | Tool | Key Parameters |
|---|---|---|
| Find sprints or releases | search_tasks | findQuery, projectId |
| Get sprint/release details | get_tasks | taskIds |
| Create a new sprint | create_item | type: "sprint", projectId, name, start?, finish? |
| Create sprint after an item | create_item | type: "sprint", projectId, name, previousItemId |
| Create a release milestone | create_item | type: "release", projectId, name, date? |
| Create release after an item | create_item | type: "release", projectId, name, previousItemId |
| Commit item to sprint | commit_to_sprint | taskId, sprintId |
| Remove item from sprint | uncommit_from_sprint | taskId |
| Update sprint members/dates | update_item | itemId, allocations |
| Add all project members to sprint | update_item | itemId, allocations: { allProjectMembers: true } |
| Assign work | update_item | itemId, assignedTo: [{ userID }] (must be sprint member) |
| Update estimates | update_item | itemId, points / estimatedDays |
| Set sprint priority | update_item | itemId, sprintPriority |
| Tag item to release | update_item | itemId, releases: [releaseId, ...] |
| Get project members | list_project_users | projectId |
| Add release notes | post_comment | releaseId, text |
Items with a committedToProjectID are already committed to a sprint. Before modifying, moving, or breaking down committed items, always confirm with the user first. When creating sub-tasks under a committed parent (parentItemId), call get_tasks on the parent first — if it has committedToProjectID, ask the user whether the sub-items should be created in the sprint or in the backlog.
