dev-context
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 context entry point for a fresh agent or a task that needs a complete project view. It reads the project records in a fixed order, so the plan, current state, and documented decisions are interpreted against the architecture and standards that govern them. It prepares a session; it does not replace the narrower records each delivery skill must read for its own work.
This skill is read only. It does not repair stale documents or change code. Report contradictions with the document and owner that must resolve them.
The files this skill ships
roles/planner.md,roles/developer.md,roles/designer.md,roles/coordinator.md,roles/reviewer.md: the protocol for each default role. Read the one the argument named, and never the others.roles/writing-a-role.md: the shape a project's own role file needs, and where it goes. Read it only when a named role has no file, or when somebody asks how to add one.