p4-plan-planning — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited p4-plan-planning (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 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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.