Configure model settings for commands, agents, and skills

Set explicit model preferences to optimize for speed vs capability:

- haiku: 11 commands, 2 agents (issue-worker, pr-fixer), 10 skills
  Fast execution for straightforward tasks

- sonnet: 4 commands (groom, improve, plan-issues, review-pr),
  1 agent (code-reviewer)
  Better judgment for analysis and review tasks

- opus: 2 commands (arch-refine-issue, arch-review-repo),
  1 agent (software-architect)
  Deep reasoning for architectural analysis

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-11 00:05:40 +01:00
parent a4c09b8411
commit bbd7870483
27 changed files with 28 additions and 2 deletions

View File

@@ -1,5 +1,6 @@
---
name: issue-worker
model: haiku
description: Autonomous agent that implements a single issue in an isolated git worktree
# Model: sonnet provides balanced speed and capability for implementation tasks.
# Implementation work benefits from good code understanding without requiring

View File

@@ -1,5 +1,6 @@
---
name: pr-fixer
model: haiku
description: Autonomous agent that addresses PR review feedback in an isolated git worktree
# Model: sonnet provides balanced speed and capability for addressing feedback.
# Similar to issue-worker, pr-fixer benefits from good code understanding

View File

@@ -1,5 +1,6 @@
---
description: Refine an issue with architectural perspective. Analyzes existing codebase patterns and provides implementation guidance.
model: opus
argument-hint: <issue-number>
---

View File

@@ -1,5 +1,6 @@
---
description: Perform a full architecture review of the current repository. Analyzes structure, patterns, dependencies, and generates prioritized recommendations.
model: opus
argument-hint:
context: fork
---

View File

@@ -1,5 +1,6 @@
---
description: Create a new Gitea issue. Can create single issues or batch create from a plan.
model: haiku
argument-hint: [title] or "batch"
---

View File

@@ -1,5 +1,6 @@
---
description: Create a new repository with standard structure. Scaffolds vision.md, CLAUDE.md, and CI configuration.
model: haiku
argument-hint: <repo-name>
context: fork
---

View File

@@ -1,5 +1,6 @@
---
description: Groom and improve issues. Without argument, reviews all open issues. With argument, grooms specific issue.
model: sonnet
argument-hint: [issue-number]
---

View File

@@ -1,5 +1,6 @@
---
description: Identify improvement opportunities based on product vision. Analyzes gaps between vision goals and current backlog.
model: sonnet
argument-hint:
context: fork
---

View File

@@ -1,5 +1,6 @@
---
description: View and manage the organization manifesto. Shows identity, personas, beliefs, and principles.
model: haiku
argument-hint:
---

View File

@@ -1,5 +1,6 @@
---
description: Plan and create issues for a feature or improvement. Breaks down work into well-structured issues with vision alignment.
model: sonnet
argument-hint: <feature-description>
context: fork
---

View File

@@ -1,5 +1,6 @@
---
description: Run a retrospective on completed work. Captures insights as issues for later encoding into skills/commands/agents.
model: haiku
argument-hint: [task-description]
---

View File

@@ -1,5 +1,6 @@
---
description: Review a Gitea pull request. Fetches PR details, diff, and comments. Includes both code review and software architecture review.
model: sonnet
argument-hint: <pr-number>
---

View File

@@ -1,5 +1,6 @@
---
allowed-tools: Bash, Task, Read, TaskOutput
model: haiku
description: Orchestrate parallel issue implementation with review cycles
argument-hint: <issue-number> [<issue-number>...]
---

View File

@@ -1,5 +1,6 @@
---
allowed-tools: Bash, Task, Read
model: haiku
description: Spawn parallel background agents to address PR review feedback
argument-hint: [pr-number...]
---

View File

@@ -1,5 +1,6 @@
---
description: Update or create CLAUDE.md with current project context. Explores the project and ensures organization context is present.
model: haiku
argument-hint:
context: fork
---

View File

@@ -1,5 +1,6 @@
---
description: View the product vision and goal progress. Manages vision.md and Gitea milestones.
model: haiku
argument-hint: [goals]
---

View File

@@ -1,5 +1,6 @@
---
description: Work on a Gitea issue. Fetches issue details and sets up branch for implementation.
model: haiku
argument-hint: <issue-number>
---

View File

@@ -1,5 +1,6 @@
---
name: backlog-grooming
model: haiku
description: Review and improve existing issues for clarity and actionability. Use when grooming the backlog, reviewing issue quality, cleaning up stale issues, or when the user wants to improve existing issues.
user-invocable: false
---

View File

@@ -133,7 +133,7 @@ Location: `commands/<name>.md`
---
description: What this command does (one-line summary)
argument-hint: <required> [optional]
model: sonnet
model: haiku
---
# Command Title
@@ -165,7 +165,7 @@ Location: `agents/<name>/AGENT.md`
---
name: agent-name
description: What this agent does and when to spawn it
model: sonnet
model: haiku
skills: skill1, skill2
disallowedTools:
- Edit

View File

@@ -1,5 +1,6 @@
---
name: claude-md-writing
model: haiku
description: Write effective CLAUDE.md files that give AI assistants the context they need. Use when creating new repos, improving existing CLAUDE.md files, or setting up projects.
user-invocable: false
---

View File

@@ -1,5 +1,6 @@
---
name: code-review
model: haiku
description: Review code for quality, bugs, security, and style issues. Use when reviewing pull requests, checking code quality, looking for bugs or security vulnerabilities, or when the user asks for a code review.
user-invocable: false
---

View File

@@ -1,5 +1,6 @@
---
name: gitea
model: haiku
description: View, create, and manage Gitea issues and pull requests using tea CLI. Use when working with issues, PRs, viewing issue details, creating pull requests, adding comments, merging PRs, or when the user mentions tea, gitea, issue numbers, or PR numbers.
user-invocable: false
---

View File

@@ -1,5 +1,6 @@
---
name: issue-writing
model: haiku
description: Write clear, actionable issues with proper structure and acceptance criteria. Use when creating issues, writing bug reports, feature requests, or when the user needs help structuring an issue.
user-invocable: false
---

View File

@@ -1,5 +1,6 @@
---
name: repo-conventions
model: haiku
description: Standard structure and conventions for Flowmade repositories. Use when creating new repos, reviewing repo structure, or setting up projects.
user-invocable: false
---

View File

@@ -1,5 +1,6 @@
---
name: roadmap-planning
model: haiku
description: Plan features and break down work into implementable issues. Use when planning a feature, creating a roadmap, breaking down large tasks, or when the user needs help organizing work into issues.
user-invocable: false
---

View File

@@ -1,5 +1,6 @@
---
name: software-architecture
model: haiku
description: >
Architectural patterns for building systems: DDD, Event Sourcing, event-driven communication.
Use when implementing features, reviewing code, planning issues, refining architecture,

View File

@@ -1,5 +1,6 @@
---
name: vision-management
model: haiku
description: Create, maintain, and evolve organization manifesto and product visions. Use when working with manifesto.md, vision.md, milestones, or aligning work with organizational direction.
user-invocable: false
---