Write Product Content
Write for the person who will use the result. Lead with their outcome, use the product's actual vocabulary, and keep only details that change understanding or action.
Workflow
- Identify the audience, desired action or decision, authoritative sources, required format, and approved presentation constraints.
- Extract concrete capabilities, boundaries, commands, and evidence from those sources. Mark unresolved claims instead of filling gaps with plausible prose.
- Draft the shortest complete structure for the reader's journey.
- Remove generic openings, throat-clearing, repeated conclusions, fake quotations, inflated significance, vague benefits, symmetrical filler, and narration about the writing process.
- Replace abstract claims with supported outcomes, examples, or exact commands. Delete claims that cannot be supported.
- Preserve established labels, ordering, links, code samples, data, and visual composition unless redesign is explicitly authorized.
- Read the final text as the intended user and verify that every paragraph earns its place.
Exclude private paths, credentials, internal deliberation, diagnostics, and local-only context from shared or public content. Do not add release or implementation history unless the requested artifact and source of truth require it.
1---2name: write-product-content3description: Write or revise reader-facing product documentation, release text, README copy, UI copy, or technical explanations using concrete evidence and no internal process narration.4---56# Write Product Content78Write for the person who will use the result. Lead with their outcome, use the product's actual vocabulary, and keep only details that change understanding or action.910## Workflow11121. Identify the audience, desired action or decision, authoritative sources, required format, and approved presentation constraints.132. Extract concrete capabilities, boundaries, commands, and evidence from those sources. Mark unresolved claims instead of filling gaps with plausible prose.143. Draft the shortest complete structure for the reader's journey.154. Remove generic openings, throat-clearing, repeated conclusions, fake quotations, inflated significance, vague benefits, symmetrical filler, and narration about the writing process.165. Replace abstract claims with supported outcomes, examples, or exact commands. Delete claims that cannot be supported.176. Preserve established labels, ordering, links, code samples, data, and visual composition unless redesign is explicitly authorized.187. Read the final text as the intended user and verify that every paragraph earns its place.1920Exclude private paths, credentials, internal deliberation, diagnostics, and local-only context from shared or public content. Do not add release or implementation history unless the requested artifact and source of truth require it.
MrMaxie