dev-scope

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 front door of the workflow, and the answer to one question: what is being built, and for whom.

Surveys the project root, fills .konteksto/project-overview.md and .konteksto/glossary.md, and records the person's scope choices in .konteksto/human-decisions.md, using the templates in this skill's own folder, then stops.

It does not answer how. Stack, structure, conventions, tooling, and the build order all belong to /dev-architect, and every one of those documents reads this file as its input.

Where this sits

Before this: nothing. This is the front door.

After this: /dev-architect, which settles how it gets built, and then /dev-design on a project with a frontend, which settles how it looks.