authoring-designslisted

# Authoring Designs The design-author's procedure: confirm repo scope, resolve open questions autonomously as recorded assumptions, and write `design.md` from the template below. Write the prose this skill governs at a seventh-grade reading level, in STE-flavored mode — short sentences, common words, no unexplained jargon. Full methodology: `writing-prose`. Before you finalize prose this skill governs, call the Skill tool with `writing-prose` and apply its `## Self-lint` checklist. If `task.md` references a `prd.md`, read it first and treat its scope boundaries and acceptance criteria per the "Consuming a PRD downstream" section of `skills/product-requirements-doc/SKILL.md`. ## Confirm repo scope (before drafting) If `docs/plans/<id>/repos.md` is **present**, read it and treat the listed repos as the working assumption. The design must respect that scope — note in `## Decisions made` which repos each decision touches and why. If `repos.md` is **absent**, scan `research.md` for signals that the work plausibly spans more than one repo (cross-service contracts, shared schemas, references to "the other repo"). When you see such signals, resolve each candidate repo autonomously through the sibling directories of the home repo root. First **validate every candidate `<name>` against a strict allowlist**: the name must match `^[A-Za-z0-9._-]+$` and must not be exactly `.` or `..`. Anything else — path separators, absolute paths, traversal sequences, shell metacharacters — fails