p4-plan-backlog-refinement — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited p4-plan-backlog-refinement (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.