long-document-segmented-writing
Write or revise long, source-grounded documents that need staged drafting or recovery.
来源信息
- 仓库
- Rycen7822/Frontier-Agent-skills
- 最近来源活动
- 2026年9月8日 12:44
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 1
- 分支
- 0
安装方式
默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。
检查来源文件
决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。
文件资源管理器
6 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- long-document-segmented-writing
- description
- Write or revise long, source-grounded documents that need staged drafting or recovery.
- metadata
- {"version":"3.0.0","author":"Hermes Agent","hosts":["codex","hermes-agent"],"hermes":{"tags":["documentation","long-form","research","planning"],"category":"software-development","related_skills":["writing-plans"]}}
# Long Document Segmented Writing
Produce the requested document with traceable source support and a coherent final argument. Match the audience, scope and output format; activating this skill does not require a long response or a separate writing workspace.
Start from the required claims and nearest relevant sources. Read bounded sections, distinguish observations from inference, and retain qualifiers that limit a source's claim. Resolve material conflicts against the owning source; mark inaccessible evidence as a limit. Do not expand source collection once the requested conclusions are supported.
Write directly to the deliverable when the work fits the current context. When reading, drafting or interruption would otherwise lose decisions, use one existing task note or the [recovery guidance](references/recovery.md). Choose this from actual recovery needs, not fixed file, byte or section counts.
Draft in coherent sections and make the final document understandable without the conversation. Keep prose paragraphs on one physical line; use structural line breaks for Markdown. Preserve requested relationships and distinctions, not merely isolated facts.
Use [segmented assembly](references/assembly.md) when independently maintained draft pieces need to become one artifact. Direct writing does not require shards or an assembly run.
Review the complete deliverable for source support, missing requirements, contradictions, terminology, transitions and working references. Reopen exact sources to repair concrete gaps, then check the affected result. Stop when the document is complete and sufficiently supported; report the deliverable and any material evidence limits. Keep internal recovery notes out of reader-facing prose unless requested.
在 GitHub 查看