Pac Update Status
Update PAC ticket status and track progress in Product as Code workflow
npx claude-code-templates@latest --command project-management/pac-update-status Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Update PAC Ticket Status
Update ticket status and track progress in Product as Code workflow: $ARGUMENTS
PAC Environment Check
- PAC directory: !
ls -la .pac/ 2>/dev/null || echo "No .pac directory found" - Active tickets: !
find .pac/tickets/ -name "*.yaml" 2>/dev/null | wc -l - Recent updates: !
find .pac/tickets/ -name "*.yaml" -mtime -7 2>/dev/null | wc -l
Task
Update PAC ticket status and track development progress:
Arguments:
- --ticket : Ticket ID to update (or select interactively)
- --status : New status (backlog/in-progress/review/blocked/done/cancelled)
- --assignee : Update assignee
- --comment : Add progress comment
- --epic : Filter tickets by epic for selection
Status Update Process:
- Validate PAC environment and locate ticket
- Load current ticket state and validate status transitions
- Update ticket YAML with new status and timestamp
- Handle status-specific actions (branch creation, PR suggestions)
- Update parent epic with ticket progress
- Generate status update summary with next actions
Valid Status Transitions: backlog→in-progress→review→done, with blocked/cancelled as intermediate states.
Git Integration: Suggests branch creation for in-progress, PR creation for review, and merge for done status.