Files
Dani 054c0e56e9 fix(commands): Remove deprecated 'model: sonnet' field from 142 command files
Removed the deprecated 'model: sonnet' field from command frontmatter to fix
compatibility issues with Claude Code. Commands will now inherit the model from
the active conversation instead of using a hardcoded deprecated model identifier.

Changes:
- Removed 'model: sonnet' from 142 command files across all categories
- Commands now use default model inheritance behavior
- Preserved 'model: claude-sonnet-4-5-20250929' in gemini-review.md (valid model)
- 67 commands without model field remain unchanged

This resolves the "model: sonnet not found" error reported in GitHub issues
and aligns with Claude Code's recommended practice of letting commands inherit
the conversation model.

Affected categories:
- Database/Supabase commands (8 files)
- Documentation commands (8 files)
- Deployment commands (11 files)
- Setup commands (14 files)
- Performance commands (8 files)
- Team commands (14 files)
- Security commands (6 files)
- NextJS/Vercel commands (10 files)
- Sync commands (14 files)
- And more across other categories

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 10:08:58 -04:00

1.5 KiB

allowed-tools: Read, Write, Edit, Bash argument-hint: [ticket-name] | --epic | --type | --assignee | --priority description: Create new PAC ticket within an epic following Product as Code specification

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:

  1. Validate PAC configuration exists (suggest /project:pac-configure if missing)
  2. Select or validate parent epic
  3. Generate unique ticket ID and sequence number
  4. Create ticket YAML file following PAC v0.1.0 specification in .pac/tickets/[ticket-id].yaml
  5. Include required metadata: id, name, epic, created timestamp, assignee
  6. Add spec with description, type, status, priority, acceptance criteria, tasks
  7. Link ticket to parent epic
  8. 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.