temperlisted
Install: claude install-skill SungJun1217/oh-my-harness-cowork
# /temper — one unit of work, hardened by review, committed on a feature branch, merged into develop
Task: $ARGUMENTS
You (the main session) orchestrate and write the commit. Talk to the user in Korean.
## 0. Scope check
- If `$ARGUMENTS` is empty or too vague to define "done", ask the user one focused question and stop.
- If it is clearly several independent units, propose the split and ask which to do first. One `/temper` = one commit.
- If the working tree already has uncommitted changes unrelated to this task, stop and ask — do not fold them into this commit.
## 0.5 Branch
Branch model (see `AGENTS.md`): `main` = released only, `develop` = integration, one `feature/<slug>` per unit.
- `git switch develop` (if it does not exist locally, stop and ask — do not create it from `main` on your own).
- `git switch -c feature/<slug>`, where `<slug>` is a short kebab-case name for this unit.
- If already on a `feature/*` branch the user set up for this task, stay on it.
- Never commit to `main` or `develop` directly.
## 1. Analyze (only when needed)
Skip this when the task already names the files and the intended behavior.
Otherwise spawn `omhc-analyst` with the task and whatever you know. Use its conclusion,
evidence, and invariants-touched list to write a precise brief for step 2.
If it reports "needs re-discussion" against a settled decision, stop and bring that to the user.
## 2. Implement
Spawn `omhc-implementer` with a concrete brief: files, intended behavior, inva