feat: add explicit model specification to workflow commands

[sjnims]

Summary

• Add model: sonnet frontmatter field to /plugin-dev:create-plugin and /plugin-dev:create-marketplace commands
• Ensures consistent workflow quality regardless of user's current conversation model

Problem

Fixes #137

Complex 8-phase workflows inherit model from conversation context, causing inconsistent quality. Users on haiku would get different results than those on opus.

Solution

Explicitly specify model: sonnet for workflow commands - a good balance of capability and cost for complex multi-step workflows.

Alternatives Considered

• Keep inheriting from conversation (original behavior): Allows user cost/quality control but risks inconsistent results
• Use opus: Maximum quality but higher cost for 8-phase workflows
• Use haiku: Faster but may not handle complex design phases well

Changes

• plugins/plugin-dev/commands/create-plugin.md: Added model: sonnet to frontmatter
• plugins/plugin-dev/commands/create-marketplace.md: Added model: sonnet to frontmatter

Testing

• Linting passes
• No structural changes to command content

---

🤖 Generated with Claude Code

[claude]

Claude finished @sjnims's task in 1m 41s —— View job

---

PR Review Complete ✓

Summary

Looks good! This PR makes a smart, targeted change that improves consistency for complex workflow commands.

---

What's Good

1. Well-scoped change: Adds exactly one line to each command file - model: sonnet in frontmatter
2. Solves real problem: Ensures 8-phase workflows have consistent quality regardless of user's conversation model (fixes [Feature]: Consider explicit model specification for workflow commands #137)
3. Smart model choice: sonnet is the right balance of capability and cost for these complex multi-step workflows
4. Already documented: The model field is properly documented in plugins/plugin-dev/skills/command-development/references/frontmatter-reference.md:130-202
5. Markdown linting: Both files pass markdownlint with no issues
6. Consistent with existing patterns: Other workflow commands use similar frontmatter structure

---

Validation Results

✅ Markdown Linting: No issues found
✅ Command Frontmatter: Valid YAML, all fields properly formatted
✅ Placement: model: sonnet added in correct position in frontmatter (between allowed-tools and disable-model-invocation)
✅ Documentation: model field already documented in command-development skill references
✅ Consistency: Both commands updated identically

---

Alternatives Analysis (from PR description)

The PR description thoughtfully considers alternatives:

• ✅ Chosen: sonnet - Good balance for complex workflows
• ❌ Keep inheriting - Causes inconsistent results (the original problem)
• ❌ Use opus - Unnecessarily expensive for 8-phase workflows
• ❌ Use haiku - May struggle with complex design phases

Agreement: sonnet is the right choice here. These are complex, multi-phase workflows that need reliable reasoning, but don't require opus-level capabilities.

---

No Documentation Updates Needed

CLAUDE.md already documents these commands (lines 178 and 191) but doesn't specify their model usage - which is appropriate since that's an implementation detail documented in the frontmatter reference.

---

Final Verdict

Approve and merge. This is a clean, well-reasoned change that:

• Solves a real consistency problem
• Uses the appropriate model tier
• Follows existing patterns
• Passes all validation
• Requires no additional documentation

Great work on identifying and fixing this issue!