메뉴
Guide backlog refinement sessions, story refinement, estimation, and prioritization in P4 Plan. Use when user mentions backlog, refinement, estimation, story points, or prioritization.
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 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.
Guide Gantt chart scheduling, scheduled tasks, dependencies, and timeline planning in P4 Plan. Use when user mentions Gantt, scheduling, timeline, dependencies, duration, start date, end date, or waterfall.
| name | p4-plan-backlog-refinement |
| description | Guide backlog refinement sessions, story refinement, estimation, and prioritization in P4 Plan. Use when user mentions backlog, refinement, estimation, story points, or prioritization. |
The Product Backlog is a dedicated section containing user stories and tasks not yet scheduled into sprints.
| User Intent | Tool | Key Parameters |
|---|---|---|
| Find backlog items | search_tasks | findQuery, projectId |
| Create a backlog item | create_item | type: "backlog_task", projectId, name |
| Create a sub-task | create_item | type: "backlog_task", projectId, name, parentItemId |
| Insert after an item | create_item | type: "backlog_task", projectId, name, previousItemId |
| Set priority | update_item | itemId, priority |
| Estimate in points | update_item | itemId, points |
| Estimate in days | update_item | itemId, estimatedDays |
| Get full item details | get_tasks | taskIds |
| Add acceptance criteria | post_comment | taskId, text |
| Move item to sprint | commit_to_sprint | taskId, sprintId |
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.
