briefings

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Briefings

页面简报

Help the user express their page vision as briefings that capture business intent. A briefing can be as lightweight as a single sentence of intent, or as detailed as final copy and image direction — the user chooses the fidelity.

帮助用户将其页面愿景转化为能体现业务目标的简报。简报可以简单到仅用一句话描述目标，也可以详细到包含最终文案和图片方向——具体粒度由用户决定。

When to use this skill

何时使用此技能

The user wants to plan pages, write briefings, define audience or CTAs, or map shared sections across pages.
The user asks to change, refine, review, critique, or iterate on any file under
```
stardust/briefings/**/*.md
```
(including
```
_site.md
```
).
The user types
```
/stardust:briefings
```
.

用户需要规划页面、撰写简报、定义受众或CTA，或映射跨页面共享板块。
用户要求修改、优化、审核、点评或迭代
```
stardust/briefings/**/*.md
```
路径下的任意文件（包括
```
_site.md
```
）。
用户输入
```
/stardust:briefings
```
。

Do NOT use this skill

请勿使用此技能

For brand identity (voice, colors, typography). Hand off to
```
brand
```
.
For structural wireframes or layout decisions. Hand off to
```
wireframes
```
or
```
prototype
```
.
To render pages. Hand off to
```
wireframes
```
(grey) or
```
prototype
```
(branded).

用于品牌标识（语气、色彩、字体）。请转交
```
brand
```
技能处理。
用于结构线框或布局决策。请转交
```
wireframes
```
或
```
prototype
```
技能处理。
用于页面渲染。请转交
```
wireframes
```
（灰度版）或
```
prototype
```
（品牌版）技能处理。

Pre-flight

前置准备

Run the procedure in

../_shared/preflight.md

first.

先执行

../_shared/preflight.md

中的流程。

Contract

约定

Needs (reads if present):

User description of pages to plan
```
.impeccable.md
```
(tone hints)
```
stardust/brand-profile.json
```
(voice; not required)

Produces:

```
stardust/briefings/_site.md
```
(multi-page only)
```
stardust/briefings/{page}.md
```
(one per page; sole source of truth for page copy)

If missing:

No input at all → ask the user which pages they need and start with the most important one.
No brand-profile.json → briefings still proceed; tone defaults to neutral-technical.

需要读取的内容（若存在）：

用户对需规划页面的描述
```
.impeccable.md
```
（语气提示）
```
stardust/brand-profile.json
```
（语气风格；非必填）

生成的内容：

```
stardust/briefings/_site.md
```
（仅适用于多页面站点）
```
stardust/briefings/{page}.md
```
（每个页面对应一份；页面文案的唯一权威来源）

缺失内容时的处理：

无任何输入 → 询问用户需要哪些页面，从最重要的页面开始。
无brand-profile.json → 仍可继续撰写简报；语气默认为中性技术风格。

Copy Ownership

文案所有权

Briefings own page copy. If the user wants final words baked in, put them in

# Copy

per section. Design will use those strings verbatim and will never rewrite them. Briefings without

# Copy

are valid — downstream skills synthesize on-brand copy and stamp provenance.

简报拥有页面文案的所有权。如果用户希望确定最终文案，请将其放在每个板块的

# Copy

部分。设计环节会直接使用这些内容，绝不会重写。没有

# Copy

的简报也是有效的——下游技能会生成符合品牌风格的文案并标注来源。

Phase 1: Scope

阶段1：范围确定

If no briefings exist yet:

Ask the user: "What pages do you need? Let's start with the most important one."
For multi-page sites, create
```
stardust/briefings/_site.md
```
first — see briefing-format.md for the site briefing schema.
Default to the structured shape for every page. Do NOT ask the user to pick a fidelity level. If a section's content is not known yet, emit
```
[TBD]
```
in that section — downstream skills synthesize on-brand content for
```
[TBD]
```
fields and stamp provenance. Fidelity is a consequence of how much the user fills in, not a gate the user has to cross.
Deepening the fidelity ladder:
- Structured (default) — full frontmatter + Intent + Audience + Key Messages + CTAs + Tone. Any field may be
```
[TBD]
```
  .
- Fully specified — adds
```
# Copy
```
  (final headlines/body/microcopy) and
```
# Imagery
```
  (image direction per section, source hints, alt-text). Reached by filling in those sections, not by re-answering a fidelity question.

If briefings already exist, read

stardust/briefings/

and confirm which pages are covered. Ask which page to work on next (new, edit, or deepen by filling in

[TBD]

fields or adding

# Copy

# Imagery

如果尚未存在任何简报：

询问用户："您需要哪些页面？我们从最重要的页面开始吧。"
对于多页面站点，先创建
```
stardust/briefings/_site.md
```
——站点简报的格式请参考briefing-format.md。
默认每个页面都采用结构化格式。请勿让用户选择粒度级别。如果某个板块的内容尚未确定，在该板块中填写
```
[TBD]
```
——下游技能会为
```
[TBD]
```
字段生成符合品牌风格的内容并标注来源。粒度级别由用户填写的内容多少决定，而非需要用户跨越的门槛。
粒度深化层级：
- 结构化（默认） — 完整的前置元数据 + 目标意图 + 受众群体 + 核心信息 + CTAs + 语气风格。任何字段都可填写
```
[TBD]
```
  。
- 完全指定 — 新增
```
# Copy
```
  （最终标题/正文/微文案）和
```
# Imagery
```
  （各板块的图片方向、来源提示、替代文本）。通过填写这些板块达到该粒度，而非重新回答粒度问题。

如果已经存在简报，读取

stardust/briefings/

下的内容并确认已覆盖哪些页面。询问用户接下来要处理哪个页面（新建、编辑，或通过填充

[TBD]

字段、添加

# Copy

# Imagery

来深化粒度）。

Phase 2: Draft

阶段2：草稿撰写

Run the soft-deps discovery decision before any interview question:
If
/brainstorm
is registered in this session (detect per
```
../_shared/soft-deps.md
```
): hand off to
```
/brainstorm
```
with a seeded prompt that includes the page name and any existing briefing content, and ask it to produce the structured shape (Intent + Audience + Key Messages + CTAs + Tone). Wait for its output; use the result to populate the briefing. Do NOT run any inline interview question once this delegation is made — that would double-interview the user.
Otherwise (superpowers not installed): announce the fallback exactly once per session, using the verbatim text from
```
../_shared/soft-deps.md
```
("superpowers announcement"). Then run the "For briefings discovery" pattern in
```
../_shared/fallback-brainstorm.md
```
. On every subsequent briefing in the same session, skip the announcement (already seen) and run the inline pattern directly.
Either path uses the same discovery prompts: "What should visitors feel when they land on this page? What's the one action you want them to take?"
The user must be able to tell which path ran — either by
```
/brainstorm
```
's visible hand-off UI or by the one-time announcement. Silent inline interviews are a bug.
Draft the briefing in the structured shape. Fill every section; where the user has not provided content, write
```
[TBD]
```
verbatim (not a rephrased placeholder). The agent helps draft; the user owns the content.
Present the draft and wait for approval before writing the file.
Write approved briefings to
```
stardust/briefings/{page}.md
```
.

If any

[TBD]

fields remain, or the briefing was synthesized from a short prompt rather than a full conversation, stamp a provenance comment at the top of the file per

../_shared/skill-contract.md

so downstream skills know which fields to treat as synthesizable.

在提出任何访谈问题前，先执行软依赖发现决策：
如果本次会话中已注册
/brainstorm
（根据
```
../_shared/soft-deps.md
```
检测）：将任务转交
```
/brainstorm
```
，并提供包含页面名称和现有简报内容的种子提示，要求其生成结构化格式（目标意图 + 受众群体 + 核心信息 + CTAs + 语气风格）。等待其输出结果，并用该结果填充简报。一旦转交任务，请勿再执行任何内置访谈问题——否则会重复询问用户。
否则（未安装增强功能）： 在本次会话中仅宣布一次备用方案，使用
```
../_shared/soft-deps.md
```
中的原文（"增强功能提示"）。然后执行
```
../_shared/fallback-brainstorm.md
```
中的"简报发现"模式。在同一会话中处理后续简报时，跳过提示直接执行内置模式。
两种路径使用相同的发现提示："用户访问此页面时应有怎样的感受？您希望他们采取的核心行动是什么？"
用户必须能区分使用的是哪种路径——要么通过
```
/brainstorm
```
的可见转交界面，要么通过一次性提示。静默内置访谈属于错误操作。
以结构化格式撰写简报。填充所有板块；如果用户未提供内容，直接填写
```
[TBD]
```
（不要使用改写的占位符）。助手协助撰写，但内容所有权归用户。
展示草稿，等待用户批准后再写入文件。
将批准后的简报写入
```
stardust/briefings/{page}.md
```
。

如果仍有

[TBD]

字段，或简报是通过简短提示而非完整对话生成的，请在文件顶部添加

../_shared/skill-contract.md

中规定的来源注释，以便下游技能知道哪些字段可生成内容。

Phase 2.5: Content Reuse Map (Multi-Page Sites Only)

阶段2.5：内容复用映射（仅适用于多页面站点）

Before the user moves on to wireframes, plan how pages connect through shared content. This is not just cross-links — it's content reuse: the same recipe card, testimonial quote, or capability highlight appears on multiple pages, authored once.

Identify the main content types each page owns (e.g., recipes page owns recipe cards, stories page owns testimonials).
Map where each content type gets reused as excerpts on other pages.
Add a
```
# Content Reuse Map
```
section to
```
stardust/briefings/_site.md
```
— see briefing-format.md for the table format.
Present the map to the user for approval before closing the stage.

Key principles:

The homepage is a hub — it should pull excerpts from every major content page.
Inner pages cross-link to at least 2 siblings through reused content sections (not just nav links).
Reused sections show 3–4 items from a source that has more, creating "see more" motivation.
Every reused section includes a CTA to the source page.

在用户进入线框环节前，规划页面如何通过共享内容建立关联。这不仅是交叉链接——而是内容复用：同一食谱卡片、客户评价或功能亮点会出现在多个页面，只需撰写一次。

确定每个页面所承载的主要内容类型（例如，食谱页面承载食谱卡片，故事页面承载客户评价）。
映射每种内容类型作为摘录在其他页面的复用位置。
在
```
stardust/briefings/_site.md
```
中添加
```
# Content Reuse Map
```
板块——表格格式请参考briefing-format.md。
向用户展示映射图，获得批准后再结束此阶段。

核心原则：

首页是枢纽 — 应从所有主要内容页面提取摘录。
内部页面通过复用内容板块至少与2个兄弟页面建立关联（而非仅通过导航链接）。
复用板块展示来源页面中的3–4个条目（来源页面应有更多条目），以此激发用户的"查看更多"意愿。
每个复用板块都包含指向来源页面的CTA。

Phase 3: Approval Gate

阶段3：批准节点

This is a soft gate. The user may want to write briefings for some pages now and others later.

After each briefing is approved, ask: "Another page, or are we done for now?"
When the user is done, tell them:
- If
```
stardust/brand-profile.json
```
  exists: "Briefings saved. You have brand + briefings — you can now run
```
/stardust:wireframes
```
  ."
- If not: "Briefings saved. Run
```
/stardust:brand
```
  when you're ready to capture your brand, then
```
/stardust:wireframes
```
  to render these pages."

Pipeline automation: When invoked as part of a full pipeline run, auto-approve each briefing and continue.

这是一个柔性节点。用户可能希望现在为部分页面撰写简报，之后再处理其他页面。

每份简报获得批准后，询问："继续处理下一个页面，还是暂时结束？"
当用户完成时，告知他们：
- 如果
```
stardust/brand-profile.json
```
  存在："简报已保存。您已完成品牌设置+简报撰写，现在可以运行
```
/stardust:wireframes
```
  。"
- 如果不存在："简报已保存。准备好捕捉品牌风格时，请运行
```
/stardust:brand
```
  ，之后再运行
```
/stardust:wireframes
```
  来渲染这些页面。"

流水线自动化： 作为完整流水线运行的一部分被调用时，自动批准每份简报并继续流程。

Why Briefings Are Standalone

为何简报独立存在

Briefings capture what the experience should be — intent, audience, messages. That work does not depend on having a brand. A user can:

Write briefings first, then extract brand, then wireframe.
Extract brand first, then write briefings, then wireframe.
Write briefings without ever running brand (useful for scoping conversations or paper-only planning).

Keeping briefings independent lets teams split the work: one person captures intent while another extracts the brand.

简报记录的是体验应达到的效果——目标意图、受众群体、核心信息。这项工作无需依赖品牌设置。用户可以：

先撰写简报，再提取品牌风格，最后制作线框。
先提取品牌风格，再撰写简报，最后制作线框。
无需运行品牌设置即可撰写简报（适用于范围讨论或纯纸面规划）。

保持简报独立可让团队分工协作：一人负责捕捉目标意图，另一人负责提取品牌风格。

Artifacts Written

生成的产物

File	Description
`stardust/briefings/_site.md`	Site-level briefing (multi-page only)
`stardust/briefings/{page}.md`	Page-level briefings in the structured shape (Intent + Audience + Key Messages + CTAs + Tone), with `[TBD]` placeholders where content is not yet captured. May additionally contain `# Copy` / `# Imagery` when the user has committed to final words or image direction.

文件	描述
`stardust/briefings/_site.md`	站点级简报（仅适用于多页面站点）
`stardust/briefings/{page}.md`	结构化格式的页面级简报（目标意图 + 受众群体 + 核心信息 + CTAs + 语气风格），内容未确定的位置使用 `[TBD]` 占位符。当用户确定最终文案或图片方向时，还可包含 `# Copy` / `# Imagery` 板块。