mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
054c0e56e9
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>
1.5 KiB
1.5 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [epic-name] | --name | --description | --owner
description: Create new PAC epic following Product as Code specification
Create PAC Epic
Create a new epic following the Product as Code specification with guided workflow: $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)
- Existing epics: !
ls -la .pac/epics/ 2>/dev/null | head -10
Task
Create a new Product as Code epic:
Arguments:
- Epic name (required if not using --name flag)
- --name : Epic name
- --description : Epic description
- --owner : Epic owner
- --scope : Scope definition
Epic Creation Process:
- Validate PAC configuration exists (suggest
/project:pac-configureif missing) - Generate epic ID from name (format: epic-[kebab-case-name])
- Create epic YAML file following PAC v0.1.0 specification in
.pac/epics/[epic-id].yaml - Include required metadata: id, name, created timestamp, owner
- Add spec with description, scope, success criteria, constraints, dependencies
- Create epic directory structure:
.pac/epics/[epic-id]/ - Update PAC index if
.pac/index.yamlexists - Create git branch
pac/[epic-id]if in git repository
If information is missing, prompt user interactively for epic details.
Next Steps: Use /project:pac-create-ticket --epic [epic-id] to add tickets to this epic.