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 task runner for the delivery chain. It completes one task at a time, in build plan order, through this sequence:

/dev-develop  →  /dev-check verify  →  /dev-test

After every selected task passes, the run ends with /dev-qa to check the audit register for regressions.

Verification is the acceptance gate. Route each failure from its verdict: behavioral failure to /dev-debug, promised but missing or built but not live to /dev-develop, and a prototype that is wrong or silent to /dev-design. A DONE task that fails behavior goes to /dev-debug; a missing or not live surface remains incomplete implementation work.

The runner selects only the tasks named in its argument. A bare /dev-loop resumes its saved state, or starts the next unfinished task in .konteksto/build-plan.md when there is no saved run.