---
name: writing
description: Author or revise CSE playbooks, flow docs, skill docs, and other longform prose in the operator voice. Use for new markdown, substantive prose edits, or a critique against the CSE prose constitution.
argument-hint: "<file-or-section>"
---

# Writing

## Compact MCP routing (local-only exemption)

This authoring workflow uses local files and no MCP tools. Do not substitute `cse_capabilities`, `cse_read`, `cse_apply`, `context_assemble`, or `cse_session_info` for local draft work.

Use this skill for CSE playbooks, flow docs, skill docs, and other longform prose that must sound like the operator. This is an authoring workflow, so it needs no MCP tools.

## Sources of truth

Read these before drafting or revising:

1. [Prose Constitution](../../../../../docs/flows/voice-guard/prose-constitution.md) for longform voice, structure, and the zero-tolerance patterns.
2. [Prose voice](../../shared/prose-voice.md) for Jira, Slack, and other short user-facing surfaces. Its surface-specific rubrics win when they differ from longform guidance.
3. The hand-written flowstate corpus named in the constitution when rhythm or register remains unclear.

Do not copy the constitution into this skill. The linked document owns those rules.

## Workflow

1. Read the target and identify its surface, audience, facts, quotes, identifiers, and explicit asks.
2. Read the constitution. For short operational comments or messages, read `prose-voice.md` too.
3. Draft in the target register. Preserve facts, quotes, names, links, dates, identifiers, and asks when they carry meaning on the target surface; drop identifiers the surface already provides.
4. Critique the draft against the relevant rules. Fix only the violating prose rather than broadly rewriting sound material.
5. Re-read source and output side by side. Reject invented facts, dropped directives, changed attribution verbs, and claims moved onto a different subject.
6. Run the [cse-prose-rewrite skill](../cse-prose-rewrite/SKILL.md) as the finishing pass when the user asks for operator-voice polish or the draft still reads model-shaped.

## Output rules

- Prefer concrete scenes, observable behavior, direct subject-verb sentences, and natural contractions.
- Keep the team voice (`we`) or reflective first person where the corpus does. Avoid coaching-register drift into `you`.
- For a Jira comment, the issue page already supplies the issue key, customer name, status, and assignee. Drop those redundancies and routine Jira UI instructions; keep only the new information or concrete ask.
- Do not add bot identity, source blocks, process narration, or evidence scaffolding to visible prose.
- Do not silently clean up spoken quotes.
- Report the finished prose, not the critique trace, unless the user asks for analysis.

This skill is a generation-time discipline, not a runtime gate. The constitution explains what automated voice checks do and do not enforce.