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>
1.5 KiB
1.5 KiB
allowed-tools: Read, Write, Edit, Grep, Glob
argument-hint: [feature-name] | --template | --interactive
description: Create Jobs-to-be-Done (JTBD) analysis for product features
Create Jobs-to-be-Done Document
You are an experienced Product Manager. Create a Jobs to be Done (JTBD) document 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
Required Documentation
- Product Documentation: @product-development/resources/product.md (to understand the product)
- Feature Idea: @product-development/current-feature/feature.md (to understand the feature idea)
IMPORTANT: If you cannot find the feature file, exit the process and notify the user.
Task
Create a JTBD document that captures the why behind user behavior and focuses on the problem or job the user is trying to get done:
-
Use the JTBD template from
@product-development/resources/JTBD-template.md -
Based on the feature idea, create a JTBD document that includes:
- Job statements following "When [situation], I want [motivation], so I can [expected outcome]"
- User needs and pain points analysis
- Desired outcomes from user perspective
- Competitive analysis through JTBD lens
- Market opportunity assessment
-
Output the JTBD document to
product-development/current-feature/JTBD.md
Focus on understanding the fundamental jobs users are trying to accomplish rather than technical features.