[Feature]: Consider explicit model specification for workflow commands

[sjnims]

Problem or Need

The /plugin-dev:create-plugin and /plugin-dev:create-marketplace commands are complex 8-phase workflows that involve:

• Multi-step reasoning
• Design decisions
• Code generation
• Validation coordination

Currently, these commands inherit the model from the conversation context. This means:

• Workflow quality may vary based on user's current model
• A user on haiku would get different results than one on opus
• Complex phases (like Phase 3: Detailed Design) might benefit from a specific model

Proposed Solution

Consider adding an explicit model specification to ensure consistent workflow quality:

---
description: Create plugins with guided 8-phase workflow
argument-hint: [plugin-description]
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(mkdir:*), Bash(git init:*), TodoWrite, AskUserQuestion, Skill, Task
model: sonnet
---

Recommended model: sonnet (good balance of capability and cost for complex workflows)

Component

• Type: Command
• Specific: /plugin-dev:create-plugin, /plugin-dev:create-marketplace

Alternatives Considered

• Keep inheriting from conversation (current behavior): Allows users to control cost/quality tradeoff
• Use opus: Maximum quality but higher cost for 8-phase workflow
• Use haiku: Faster but may not handle complex design phases well

Additional Context

Per official Claude Code docs:

model: Specific model string. Default: Inherits from the conversation

The phased structure of these commands already provides good guidance, so model inheritance may be sufficient. This is a low-priority optional improvement for consistency.

Priority

Low - Just a suggestion (inheriting is valid default behavior)

[sjnims]

PR submitted: #140