dev-develop

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 builder. Turns one task from build-plan.md into working code that follows code-standards.md and fits architecture.md.

Builds one task at a time, in the order the plan sets, and stamps each completed subtask Status before rolling them into the aggregate task row. The aggregate becomes DONE before starting the next task. A task with UI subtask goals builds components and pages. A task with Logic subtask goals builds APIs, services, and data layers. A task with both builds both.

It decides nothing load bearing. That is what the gate in step 1 is for.

Where this sits

Before this: /dev-architect, which settled the stack and wrote the plan, and on a project with an app/ also /dev-design, which got every surface approved.

After this: /dev-check verify, which proves the task actually works. A failure there goes to /dev-debug.