dev-architect

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

Answers how the product gets built, given a project-overview.md that already says what it is. Settles every load bearing technical decision and records the result across the documents in .konteksto/.

/dev-scope owns the what and never names a tool. This skill makes every tool call there is, including installing the browser /dev-design and /dev-check verify need.

How the product looks is /dev-design's, on a project with an app/. It owns design.md, design-registry.md, and the prototypes, and nothing here writes any of them.

Where this sits

Before this: /dev-scope, which settled what the product is.

After this: /dev-design on a project with an app/, which designs every surface the flows require and gets each one approved. On a backend with no app/, straight to /dev-develop, which builds the first real task in the plan, meaning the first one outside a Phase 0 of baseline rows where the plan has one.