返回提示词目录第 1462 页

功能规则支持说明编写

把代码和配置中的功能规则整理成支持团队可执行的说明,涵盖限制、边界情况与排查步骤。

完整提示词

<context>
Support teams learn features from marketing pages and release notes, which describe the happy path. The tickets come from the rules nobody wrote down: what happens at a limit, the order in which settings win, delays from caches and background jobs, time zones, permissions, what a plan downgrade does to existing data. Engineers know these from the code. A good explainer turns that knowledge into rules support can apply without reading code, tells them how to check a customer's situation, and separates "working as designed" from "probably a bug" so engineering gets fewer false escalations and fewer real bugs are dismissed.
</context>

<task>
Write an internal explainer of this feature for the support team.

<feature>
{{feature}}
</feature>
{{#common_questions}}
<common_questions>
{{common_questions}}
</common_questions>
{{/common_questions}}

1. If code or config paths are given and you can read them, read them first and base the rules on what the code does, noting where it differs from the spec.
2. Explain in one paragraph what the feature is for and who can use it (plans, roles, platforms).
3. Write "How it works" as plain rules: triggers, order of precedence, timing and delays, limits and what happens at them, and what happens on downgrade, deletion or expiry.
4. List edge cases and confusing behaviours that are working as designed, each with a one-line explanation support can give.
5. Write "How to check": what to look at in the admin tools or ask the customer to tell what state they are in.
6. Write "Probably a bug if": signs that should go to engineering, and what to collect.
{{#common_questions}}7. Answer each common question directly.{{/common_questions}}
</task>

<constraints>
- Only state rules supported by the input or the code you read; mark anything inferred "(confirm with engineering)".
- No internal hostnames, code identifiers or people's names in the explainer body.
- Do not promise roadmap changes or fixes.
- Write for a non-engineer; avoid jargon or explain it once.
</constraints>

<output_format>
## What it is
## How it works
## Working as designed (but confusing)
## How to check a customer's case
## Probably a bug if
## Common questions
## Unconfirmed
Points marked for engineering to confirm, or "None".
</output_format>

可替换内容

  • {{feature}}
  • {{#common_questions}}
  • {{common_questions}}
  • {{/common_questions}}

分类与标签

办公效率、客服支持、内部文档、功能说明

前往 AI 图片创作