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>
36 lines
2.0 KiB
Markdown
36 lines
2.0 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, WebSearch
|
|
argument-hint: [time-horizon] | --near-term | --medium-term | --long-term | --disruption-focus
|
|
description: Generate comprehensive future scenarios with plausibility scoring, trend integration, and strategic implications
|
|
---
|
|
|
|
# Future Scenario Generator
|
|
|
|
Generate comprehensive future scenarios with systematic analysis and strategic integration: **$ARGUMENTS**
|
|
|
|
## Current Trend Context
|
|
|
|
- Time horizon: Based on $ARGUMENTS (1-2 years, 3-5 years, 5-10+ years)
|
|
- Domain focus: Industry, technology, society, or economic scenario generation
|
|
- Existing trends: Current patterns, trajectories, and emerging developments
|
|
- Key variables: Major factors that could shape future outcomes
|
|
|
|
## Task
|
|
|
|
Create systematic future scenarios with comprehensive analysis and strategic implications:
|
|
|
|
**Time Horizon**: Use $ARGUMENTS to focus on near-term, medium-term, long-term, or disruption-focused scenarios
|
|
|
|
**Scenario Framework**:
|
|
1. **Trend Analysis** - Multi-dimensional trend identification across technology, social, economic, and regulatory domains
|
|
2. **Scenario Architecture** - Baseline, optimistic, pessimistic, and transformation scenarios with cross-impact analysis
|
|
3. **Plausibility Assessment** - Multi-criteria scoring based on historical precedent, logical consistency, and expert validation
|
|
4. **Wild Card Integration** - Low-probability, high-impact events and disruption modeling
|
|
5. **Strategic Implications** - Decision-relevant insights and robust strategy identification
|
|
6. **Monitoring Framework** - Early warning indicators and scenario tracking systems
|
|
|
|
**Advanced Features**: Monte Carlo simulations, scenario interaction modeling, confidence intervals, and adaptive scenario management.
|
|
|
|
**Decision Integration**: Connect scenarios to strategic planning, risk management, and option generation with actionable recommendations.
|
|
|
|
**Output**: Comprehensive scenario portfolio with plausibility scores, strategic implications, monitoring indicators, and decision frameworks for multiple future possibilities. |