subsection-writer
Modular writer for technical survey sections.
Install
mkdir -p .claude/skills/subsection-writer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14818" && unzip -o skill.zip -d .claude/skills/subsection-writer && rm skill.zipInstalls to .claude/skills/subsection-writer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Write survey prose into per-section files under `sections/` so each unit can be QA'd independently before merging. **Trigger**: subsection writer, per-section writing, split sections, sections/, 分小节写, 按章节拆分写作. **Use when**: `Approve C2` is recorded and writer packs exist (`outline/writer_context_packs.jsonl`); you want evidence-bounded drafting without a monolithic one-shot draft. **Skip if**: `DECISIONS.md` approval is missing, or `outline/evidence_drafts.jsonl` / `citations/ref.bib` is missing. **Network**: none. **Guardrail**: do not invent facts/citations; no TODO/ellipsis leakage; keep citations subsection- or chapter-scoped; H3 body files and chapter leads must not contain headings.Key capabilities
- →Write survey prose into per-section files
- →Ensure compatibility with existing document pipelines
- →Adhere to strict citation and H3 header constraints
- →Bootstrap missing H3 files and refresh manifest
- →Adjust paragraph-role behavior or refactor writer policy
How it works
The skill writes or refines per-section survey prose into isolated files, maintaining compatibility with the existing pipeline contract and adhering to writing guidance and machine-readable contracts.
Inputs & outputs
When to use subsection-writer
- →Draft a specific survey section
- →Refine survey prose independently
- →Write subsection content
About this skill
Subsection Writer (compatibility router)
Purpose: write or refine per-section survey prose under sections/ while keeping the current pipeline contract unchanged.
Compatibility mode:
- output paths stay the same
scripts/run.pystill handles approval checks, missing-file bootstrap, andsections/sections_manifest.jsonl- writing guidance now lives in
references/instead of being encoded primarily in the script
Load Order
Always read:
references/overview.mdreferences/paragraph_jobs.mdreferences/paragraph_job_archetypes.mdwhen adjusting paragraph-role behavior or refactoring writer policy out of Pythonreferences/bootstrap_assembly.mdwhen reasoning about compatibility-mode bootstrap behavior
Read as needed:
references/opener_catalog.mdwhen paragraph 1 sounds generic or narratedreferences/contrast_moves.mdwhen building A-vs-B comparison paragraphsreferences/eval_anchor_patterns.mdwhen making performance / robustness / benchmark claimsreferences/limitation_moves.mdwhen adding caveats or local conclusionsreferences/examples_good.mdandreferences/examples_bad.mdfor calibration only
Machine-readable contract:
assets/subsection_writer_context.schema.jsonassets/bootstrap_paragraph_templates.jsonassets/paragraph_job_templates.json
Inputs
Required:
DECISIONS.md(must includeApprove C2)outline/outline.ymloutline/writer_context_packs.jsonl(preferred)citations/ref.bib
Optional but useful:
outline/subsection_briefs.jsonloutline/evidence_drafts.jsonloutline/evidence_bindings.jsonloutline/anchor_sheet.jsonloutline/chapter_briefs.jsonl
Outputs
Keep the current contract:
sections/S<sub_id>.mdfor H3 bodiessections/sections_manifest.jsonl, refreshed across all section files already produced by the three writer Skillssections/h3_bodies.refined.okafter a model or human has reviewed the generated H3 bodies and is submitting U100 for mandatory acceptance
front-matter-writer owns Abstract, Introduction, Related Work, Discussion, and
Conclusion. chapter-lead-writer owns H2 lead blocks. This Skill reads those
files while refreshing the shared manifest but does not claim their authorship.
Writer policy
The active rule is move coverage, not paragraph quota. A subsection should cover the necessary argument moves the pack supports; do not pad to a fixed count when the evidence does not justify it.
Opener / ending policy:
- generate 2-4 opener candidates from the pack's actual tension, contrast, protocol, or limitation signals; keep the most content-bearing option instead of reusing one stock stem everywhere
- let subsection endings emerge from evidence-bearing comparison / limitation material; do not append a fixed “safest synthesis / decision rule” closer just to make the paragraph feel finished
- normalize internal axis labels into natural reader prose; slash-style brief handles should remain planning metadata, not leak unchanged into the paper
Script boundary
Use scripts/run.py as a helper only:
- it may bootstrap missing H3 files and refresh the manifest
- bootstrap prose is assembled deterministically from writer packs and the versioned template assets; it is inspectable fallback material, not a claim of model authorship or final prose quality
- it must not be treated as the canonical source of prose shape or voice policy
- it must not self-certify its bootstrap prose: the script never creates
sections/h3_bodies.refined.ok - the marker is only U100's submission attestation; it is created before the
downstream
writer-selfloop, so it cannot mean that the self-loop already passed - mandatory acceptance independently compares H3 sentences with the Run-selected writer template assets and rejects literal residue above the Pipeline limit
writer-selfloopcalls the shared strict section checker, which recomputes the H3 measure before the report can PASS- the mandatory
pipeline-auditormeasures the entire merged draft and writes a scorecard whose verdict and dimensions the Harness projects into the evaluation ledger - the current 10% limit is an initial policy target; a published current-contract replay measures 0/226 residue for one retained Artifact set, while clean from-scratch and cross-topic reproduction remain open
- if the marker predates a writer input or the writer script, it is stale and the next run removes it before regenerating bootstrap prose
Quick Start
uv run python .codex/skills/subsection-writer/scripts/run.py --workspace <workspace>
Troubleshooting
- If the pack is thin, stop and route upstream instead of padding prose.
- If the subsection sounds narrated, reload
references/opener_catalog.mdandreferences/examples_bad.md. - If a claim lacks protocol context, reload
references/eval_anchor_patterns.mdbefore rewriting.
Execution notes
When running in compatibility mode, scripts/run.py currently consumes:
DECISIONS.mdforApprove C2outline/outline.ymlto enumerate chapter / subsection filesoutline/writer_context_packs.jsonlas the primary drafting inputcitations/ref.bibfor in-scope citationsoutline/subsection_briefs.jsonl,outline/evidence_drafts.jsonl,outline/evidence_bindings.jsonl,outline/anchor_sheet.jsonl, andoutline/chapter_briefs.jsonlas optional enrichment sources
Script
Quick Start
uv run python .codex/skills/subsection-writer/scripts/run.py --workspace <workspace>
All Options
--workspace <dir>--unit-id <id>--inputs <a;b;...>--outputs <a;b;...>--checkpoint <C*>
Examples
uv run python .codex/skills/subsection-writer/scripts/run.py --workspace <workspace>
Troubleshooting
- If
DECISIONS.mdlacksApprove C2, stop and fix approval first. - If
outline/writer_context_packs.jsonlis thin, reroute upstream instead of padding prose. - If citation scope looks wrong, re-check
citations/ref.biband the writer packs before editing output text.
When not to use it
- →`DECISIONS.md` approval is missing
- →`outline/evidence_drafts.jsonl` or `citations/ref.bib` is missing
- →The user wants a monolithic one-shot draft
Limitations
- →Does not allow TODO/ellipsis leakage
- →H3 body files and chapter leads must not contain headings
How it compares
This skill enables section-by-section drafting and refinement, allowing independent QA of each unit, rather than generating a single, monolithic draft.
Compared to similar skills
subsection-writer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| subsection-writer (this skill) | 0 | 5mo | Review | Advanced |
| scientific-writing | 94 | 2mo | Review | Intermediate |
| content-research-writer | 15 | 10mo | No flags | Beginner |
| research-grants | 6 | 7mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by WILLOSCAR
View all by WILLOSCAR →You might also like
scientific-writing
K-Dense-AI
Write scientific manuscripts. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), abstracts, for research papers and journal submissions.
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
clinical-decision-support
K-Dense-AI
Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
nsfc-research-foundation-writer
huangwb8
为 NSFC 正文"(三)研究基础"写作/重构,并同步编排"工作条件"和"研究风险应对",用证据链证明项目可行、资源条件对位研究内容、风险预案可执行。适用于用户要写/改"研究基础、前期工作、可行性分析、工作条件、平台团队、风险应对"等场景。
arcanea-scene-craft
frankxai
Master scene construction - the building blocks of story. Openings that hook, middles that build, endings that propel. Turn every scene into a compelling unit of narrative.