dev-harness

Output style (plain words, no dashes, no hyphens)

Write everything this skill produces, files and messages alike, in plain simple language. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. A structural separator inside a template format other skills parse, such as the em dash in ## Phase 1 — <NAME>, is part of that format: reproduce it exactly, since changing it breaks the mirroring. Use short sentences, commas, or parentheses. Clear beats clever.

What this skill does

The delivery loop already knows what to do next. /dev-loop records Next action in .konteksto/loop-state.md, and /dev-audit records Next route for every open finding. What neither of them can do is run the next step somewhere else, on a different model, while a person is away from the keyboard.

That is this skill. It runs one agent per Herdr pane and moves recorded routes between them:

coordinator  →  developer  →  coordinator  →  reviewer  →  coordinator  →  person

• coordinator relays. It reads the route, sends it to the right pane, watches, and reaches the person when a decision is theirs.
• developer builds: /dev-loop, /dev-develop, /dev-check verify, /dev-debug, /dev-design, /dev-architect, /dev-test. It runs /dev-architect so a run does not stop at every unmade decision, and it relays every options panel rather than answering one.
• reviewer reads code it did not write: /dev-check review, /dev-audit, /dev-qa, /dev-sync. On a different model from the developer, which config enforces.