kata-set-profile
1. Validate argument
if $ARGUMENTS.profile not in ["quality", "balanced", "budget"]:
Error: Invalid profile "$ARGUMENTS.profile"
Valid profiles: quality, balanced, budget
STOP
2. Check for project
ls .planning/config.json 2>/dev/null
If no .planning/ directory:
Error: No Kata project found.
Run /kata-new-project first to initialize a project.
3. Update config.json
Read current config:
cat .planning/config.json
Update model_profile field (or add if missing):
{
"model_profile": "$ARGUMENTS.profile"
}
Write updated config back to .planning/config.json.
4. Confirm
✓ Model profile set to: $ARGUMENTS.profile
Agents will now use:
[Show table from model-profiles.md for selected profile]
Next spawned agents will use the new profile.
Switch to budget mode:
/kata-set-profile budget
✓ Model profile set to: budget
Agents will now use:
| Agent | Model |
| ------------- | ------ |
| kata-planner | sonnet |
| kata-executor | sonnet |
| kata-verifier | haiku |
| ... | ... |
Switch to quality mode:
/kata-set-profile quality
✓ Model profile set to: quality
Agents will now use:
| Agent | Model |
| ------------- | ------ |
| kata-planner | opus |
| kata-executor | opus |
| kata-verifier | sonnet |
| ... | ... |
More from gannonh/kata-skills
kata-resume-work
Resume work from a previous session, restoring context after a break, continuing work after /clear, or picking up where you left off. Triggers include "resume work", "continue work", "pick up where I left off", "restore context", and "resume session".
23kata-review-pull-requests
Run a comprehensive pull request review using multiple specialized agents. Each agent focuses on a different aspect of code quality, such as comments, tests, error handling, type design, and general code review. The skill aggregates results and provides a clear action plan for improvements. Triggers include "review PR", "analyze pull request", "code review", and "PR quality check".
22kata-list-phase-assumptions
Surface Claude's assumptions about a phase approach before planning, checking what Claude thinks, or validating understanding before planning. Triggers include "list assumptions", "what are you thinking", "show assumptions", "phase assumptions", and "what's the plan".
20kata-track-progress
Check project progress, show context, and route to next action (execute or plan). Triggers include "progress".
20kata-debug
Systematically debug issues, investigating bugs, troubleshooting problems, or tracking down errors with persistent state across context resets. Triggers include "debug", "investigate bug", "troubleshoot", "find the problem", "why isn't this working", and "debug session".
20kata-map-codebase
Analyze an existing codebase with parallel mapper agents, creating codebase documentation, understanding brownfield projects, or mapping code structure. Triggers include "map codebase", "analyze codebase", "create project context", "document codebase", "understand code", and "codebase map".
20