dev-sync
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
Closes the loop on a finished change. The .konteksto documents are only worth reading if they are true, and they drift the moment a build goes slightly differently from the plan.
This reconciles what it is allowed to, from repo evidence rather than from what anyone said, and flags the rest. The Boundaries table below is the exact contract, and it is the whole skill.
Reconciles what can be verified. Flags what needs a decision. It never guesses, and it never quietly edits a document owned by another skill.
Default to doing nothing. A change that alters no command, convention, constraint, dependency, or structural fact does not belong in durable knowledge. A line that narrates what this change did is churn, not maintenance. Finding nothing to sync is a normal, good outcome, and reporting it plainly is a complete result.
Idempotent, and that is testable. Running this twice on the same change must make zero new edits the second time. Before adding anything, read the target again and check whether the fact is already there, even worded differently. Before writing any line, read the file again, because a teammate or another session may have edited it since you looked.