section-drafter

Start with a one-paragraph overview naming the framework, pipeline, and modules, then write one subsection per module stating its purpose, technical mechanism, and implementation notes. This Skill derives that structure from a thinking template mapping each module to a specific challenge.

Structure it in three layers: a mechanism explanation tied to your key idea, explicit connections to prior work limitations, and specific limits with future work. Use hedged voice like "suggests that" and "is consistent with" rather than "proves" or "demonstrates conclusively".

No. Introduction drafting is handled by the sibling intro-drafter skill, which uses a dedicated six-paragraph framework. This Skill covers Abstract, Related Work, Methods, Results, Discussion, Conclusion, and Future Work only.

No. It only writes claims traceable to user input or scholar_search results, never invents numbers, and rephrases or omits statements when a citation cannot be verified. Placeholder tags like [citation needed] are explicitly forbidden.

It outputs flowing paragraph prose for the requested section with sequential numbered citations like [1], [2], followed by a References list. It never includes thinking templates, consistency check reports, section headers unless requested, or meta-commentary about its process.

Avoid it for Introduction sections, language polishing of existing drafts (use paper-polish), benchmark papers (use benchmark-paper-template), or submission-readiness evaluation (use doubao-academic-evaluator).