write-outcomeslisted

# Tandem: write-outcomes (dispatch-only) This skill is **dispatch-only**. Producer skills (via FEAT-14.3 wirings) spawn a sub-agent, hand it an artefact's technical scope, and this skill transforms it into a single plain-English outcome line for founder-facing communication. A human never invokes this directly; it is not part of the lifecycle command chain. An "outcome line" is the what-you-can-now-do summary: what a founder will *have* or *be able to do* after this artefact ships. It strips internals and surfaces value. ## Voice The outcome voice is one sentence, plain English, second-person or capability-framed. Hard bans (literal — keep this phrasing intentional and verbatim; TESTPLAN-14.1.01 TC-02 asserts these markers): **no internal IDs**, **no command names**, **no shell**, no jargon. Apply these strict rules: - **DO:** Write what the founder will have or be able to do (`You can now…`, `You have…`, or `Teams can…`). - **DON'T:** Use internal IDs (e.g., PROJ-12, RFC-44, TICKET-318). - **DON'T:** Name commands or implementation (e.g., slash-commands, build scripts, CLI flags). - **DON'T:** Include shell syntax, jargon, or tool names (e.g., "webhook payload," "API v3.2"). - **DO:** Keep it under ~20 words — one line, scannable. ## Template ``` You can now <capability> — <the value it unlocks>. ``` Or: `You have <artefact> enabling <outcome>.` Adapt as needed; keep it a single line. ## Examples Each pair is labelled by the artefact type whose technical body the p