mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Dani
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>
35 lines
1.5 KiB
Markdown
35 lines
1.5 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Grep, Glob
|
|
argument-hint: [feature-name] | --template | --interactive
|
|
description: Create Product Requirements Document (PRD) for new features
|
|
---
|
|
|
|
# Create Product Requirements Document
|
|
|
|
You are an experienced Product Manager. Create a Product Requirements Document (PRD) for a feature we are adding to the product: **$ARGUMENTS**
|
|
|
|
**IMPORTANT:**
|
|
- Focus on the feature and user needs, not technical implementation
|
|
- Do not include any time estimates
|
|
|
|
## Product Context
|
|
|
|
1. **Product Documentation**: @product-development/resources/product.md (to understand the product)
|
|
2. **Feature Documentation**: @product-development/current-feature/feature.md (to understand the feature idea)
|
|
3. **JTBD Documentation**: @product-development/current-feature/JTBD.md (to understand the Jobs to be Done)
|
|
|
|
## Task
|
|
|
|
Create a comprehensive PRD document that captures the what, why, and how of the product:
|
|
|
|
1. Use the PRD template from `@product-development/resources/PRD-template.md`
|
|
2. Based on the feature documentation, create a PRD that defines:
|
|
- Problem statement and user needs
|
|
- Feature specifications and scope
|
|
- Success metrics and acceptance criteria
|
|
- User experience requirements
|
|
- Technical considerations (high-level only)
|
|
|
|
3. Output the completed PRD to `product-development/current-feature/PRD.md`
|
|
|
|
Focus on creating a comprehensive PRD that clearly defines the feature requirements while maintaining alignment with user needs and business objectives. |