pac-create-ticket
Create new PAC ticket within an epic following Product as Code specification
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 9686ce6dd9861278… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
pac-create-ticket.md
Create PAC Ticket
Create a new ticket within an epic following Product as Code specification: $ARGUMENTS
PAC Configuration Check
- PAC directory: !
ls -la .pac/ 2>/dev/null || echo "No .pac directory found" - PAC config: @.pac/pac.config.yaml (if exists)
- Available epics: !
ls -la .pac/epics/ 2>/dev/null | head -10
Task
Create a new Product as Code ticket within an existing epic:
Arguments:
- Ticket name (required if not using --name flag)
- --epic : Parent epic ID (required)
- --type : Ticket type (feature/bug/task/spike)
- --assignee : Assigned developer
- --priority : Priority level
- --create-branch: Automatically create git branch
Ticket Creation Process:
- Validate PAC configuration exists (suggest
/project:pac-configureif missing) - Select or validate parent epic
- Generate unique ticket ID and sequence number
- Create ticket YAML file following PAC v0.1.0 specification in
.pac/tickets/[ticket-id].yaml - Include required metadata: id, name, epic, created timestamp, assignee
- Add spec with description, type, status, priority, acceptance criteria, tasks
- Link ticket to parent epic
- Create git branch if requested
If information is missing, prompt user interactively for ticket details.
Next Steps: Use /project:pac-update-status to track ticket progress.
Files
1- pac-create-ticket.md
96c41e92051.5 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from davila7/claude-code-templates8
Execute GitHub Actions locally using act
Implement secure user authentication system with chosen method and security best practices
Generate and maintain project changelog with Keep a Changelog format
Setup comprehensive mutation testing with framework selection and CI integration
Add and configure new package to workspace with proper structure and dependencies
Setup comprehensive application performance monitoring with metrics, alerting, and observability
Implement property-based testing with framework selection and invariant identification
Add entry to project changelog following Keep a Changelog format
Related frontend skillsscan passed
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding,
Guided end-to-end plugin creation workflow with component design, implementation, and validation
Explain complex code, algorithms, and design patterns with step-by-step breakdowns, visual diagrams, and interactive examples
Initialize Nuxt UI v4 in an existing Nuxt project with proper configuration