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에서 보기