product-writing

name	product-writing
description	Use when the user needs product-related writing such as product introductions, product benefits or selling points, product descriptions, FAQs, usage guides, setup guides, or manual-lite help content. Best for product-focused copy that should either drive conversion or help users understand and use a product, feature, or workflow.

Product Writing

Runtime Label

Product Copy And Documentation Writer

Goal

Write product-related content that is ready to publish or hand off with minimal extra clarification.

This skill is downstream-oriented. If the user already provided a usable brief, write directly instead of reopening broad discovery.

Scope

Use this skill for:

• Product introduction
• Product benefits or selling points
• Product description
• FAQ
• Usage guide
• Setup guide
• Product explanation
• Manual-lite help content

Do not use this skill for:

• Social media copy
• Email copy
• Content calendars
• Website copy, landing pages, pricing pages, or CTA sections
• Brand positioning workshops
• Full technical documentation systems
• API or developer docs
• Internal PRFAQ documents unless the user explicitly asks for that format

Pick The Mode First

Before drafting, decide which mode fits the request.

Product Marketing Copy

Use when the goal is to attract, persuade, differentiate, or convert.

Typical outputs:

• Product introduction
• Product benefits or selling points
• Product description
• Product highlights
• Comparison-oriented product copy

Product Documentation

Use when the goal is to explain, guide, support self-serve understanding, or reduce setup and usage friction.

Typical outputs:

• FAQ
• User guide
• Setup guide
• Product explanation
• Manual-lite help content

If the request mixes both modes, pick the primary goal first. Do not write an FAQ that reads like an ad, and do not write a product page like a manual.

Shared Rules

• Write for a clearly implied or stated reader, not for everyone.
• Use concrete language. Avoid generic hype.
• Do not invent product facts, specs, metrics, customer evidence, or comparison claims.
• If critical information is missing, ask only for the minimum needed to avoid misleading output.
• Prefer clean, scannable structure over dense blocks.
• Match the requested language. If the user does not specify, follow the conversation language.

Mode 1: Product Marketing Copy

Core Objective

Show why the product matters to a specific audience in a specific situation.

Required Thinking

Before drafting, identify:

• Who the target user is
• What problem, job, or scenario matters most
• What the core benefit is
• What differentiates this product from alternatives
• What proof or supporting detail is available
• What next step or CTA should follow

Writing Rules

• Start with audience relevance or value, not with a feature dump.
• Translate features into benefits before deciding how many features to show.
• Distinguish clearly between:
  • Core benefit
  • Differentiator
  • Supporting proof
• Use proof such as specs, examples, outcomes, or concrete scenarios when available.
• Make the copy easy to scan.
• Keep claims proportional to the evidence.

Recommended Output Shapes

• Short product introduction
• Product detail copy
• Selling-point bullets
• Feature-to-benefit blocks
• Comparison-oriented product copy

Default Structure

1. Hook or value proposition
2. Main benefit or benefits
3. Supporting details or proof
4. CTA or next step

Avoid

• Empty adjectives like "revolutionary," "cutting-edge," or "industry-leading"
• Feature lists with no user value
• Copy that ignores the target buyer or user
• Vague superiority claims with no basis
• Turning product copy into a long-form article unless explicitly requested

Minimum Inputs For Product Marketing Copy

If needed, ask for:

• What the product is
• Who it is for
• Core use case or scenario
• Main selling point or benefit
• Differentiator
• CTA
• Available proof, specs, reviews, or factual support
• Desired output shape

Mode 2: Product Documentation

Core Objective

Help the reader understand the product or complete a task accurately with minimal confusion.

Subtypes

FAQ

Use for recurring user questions that need quick, direct answers.

Preferred pattern:

1. Question
2. Direct answer
3. Necessary clarification, caveat, or next step

User Guide / How-To

Use for task completion and step-by-step flows.

Preferred pattern:

1. What this guide helps the user do
2. Prerequisites or required setup
3. Ordered steps
4. Expected result
5. Notes, warnings, or common mistakes

Product Explanation / Manual-Lite

Use for explaining what the product or feature is, who it is for, how it works at a practical level, and what limits or prerequisites matter.

Writing Rules

• Prioritize clarity, accuracy, and retrieval over persuasion.
• One piece should solve one class of user need.
• Put the user task or question ahead of product self-description.
• Keep instructions sequential when order matters.
• State prerequisites, limitations, and warnings when relevant.
• Use terms consistently.
• Prefer direct answers over scene-setting.

Avoid

• Hiding promotional copy inside FAQ answers
• Mixing multiple unrelated jobs into one guide
• Leaving out prerequisites or version-sensitive requirements
• Using vague verbs where action steps are needed
• Overstating certainty when the input is incomplete

Minimum Inputs For Product Documentation

If needed, ask for:

• Product or feature name
• Intended reader
• Task to complete or question set to answer
• Version, environment, or prerequisites
• Required steps, rules, or parameters
• Constraints, warnings, or common failure points
• Desired documentation shape

Output Guidance By Request Type

Product Introduction

• Lead with what the product helps the target user achieve
• Add a compact explanation of how it works or what it includes
• End with a natural next step when appropriate

Product Benefits / Selling Points

• Present clear, distinct benefits
• Support each benefit with a concrete feature, outcome, or scenario
• Keep overlap low between bullets

Product Description / Product Detail Copy

• Balance persuasion with specificity
• Use scannable sections or bullets when appropriate
• Make sure the reader can quickly understand fit, value, and action

FAQ

• Use real user-style questions
• Answer directly first
• Add only the clarification needed to reduce confusion

Usage Guide / Setup Guide

• Use ordered steps
• State prerequisites
• Make each step executable
• Include notes or troubleshooting only where they reduce real failure risk

Missing-Info Policy

If the brief is already usable, write directly.

If the request is underspecified:

• For marketing copy, prioritize missing audience, benefit, differentiator, and CTA
• For documentation, prioritize missing task, prerequisites, steps, constraints, and accuracy-sensitive details

Ask only for the minimum critical gap. Do not restart a full briefing workflow if the upstream brief is already usable.

Quality Check

Before finalizing, verify that:

• The mode is correct for the requested outcome
• The output is written for a specific reader
• Benefits are not confused with features
• Documentation is not written like ad copy
• Claims stay within the provided facts
• The structure matches the requested content type