Long Document Direct Bulk Reading Strategy
This skill is a thin entry point that breaks the long document processing into several independently maintainable modules:
references/reading-strategy.md: Bash continuous reading with each window not exceeding 23,000 characters, coverage ledger format, output path, and failure conditions.references/writing-standard.md: Specific script requirements for video account reading scripts and the final raw JSON field format.references/revision-workflow.md: Minimal but reviewable workflow for draft, structural, and final versions, including difference audit.
Body Length Configuration
This is the single source of truth for the body draft length in this skill. Other references must not duplicate specific word counts but can only reference this section.
draft_min_chars: 3000
final_target_chars: 3200
- Before saving
_draft_v1.txt, it must reachdraft_min_chars. - All subsequent body drafts must not fall below
draft_min_charsin principle. - The target length for
contentin the final raw JSON followsfinal_target_chars;total_lengthrecords the actual character count ofcontent.
Main Workflow
Do not output in one pass. Follow "Understand -> Set Angle -> Write Draft -> Multi-round Revision -> Package Output":
- Understand Material: First read
references/reading-strategy.md. Extract text, devise a Bash character window plan, establish and update the coverage ledger. - Coverage Gate: Do not write drafts, revisions, or final JSON until coverage check passes.
- Type and Angle: Silently determine the material type, extract core questions, an explanatory framework, and a sharp angle relevant to the audience.
- Draft Writing: Read
references/writing-standard.md, generate_draft_v1.txtreachingdraft_min_chars. - Multi-round Revision: Read
references/revision-workflow.md, save structural draft, final draft, and revision audit. - Package Output: From
_draft_final.txt, generate title, cover copy, quotes, intro, and final raw JSON; unless the user requests to see intermediate steps, output only the project-usable raw JSON, and ensure it is parseable byjson.loads.
Self-Check Requirements
Before submitting the final JSON, silently confirm:
- Coverage requirements have been met according to total text length segmentation, covering the beginning, middle, end, and main sections, and that
coverage_check.passed=truein the ledger matches reality. - The script complies with
writing-standard.mdregarding opening, rhythm, style, prohibited expressions, and revision requirements. - Each revision round re-reads
writing-standard.mdto ensure no requirements are forgotten. - The revision process has been saved per round as per
revision-workflow.md, the final version originates from_draft_final.txt, and the audit corresponds to the actual differences in each round. - The JSON conforms to the final JSON output contract in
writing-standard.md.