What problem does it solve? Writing a systems paper for venues like OSDI, SOSP, ASPLOS, NSDI, or EuroSys requires strict structural discipline—page budgets, paragraph roles, and argumentation patterns—that most authors learn only through repeated rejections. This Skill supplies a paragraph-level blueprint so every section has a defined purpose, length, and writing pattern. ## Core Features & Use Cases - Page Allocation Tables: Per-section page budgets for 12-page systems papers, with venue-specific format differences (USENIX vs ACM). - Section Blueprints: Sentence-level templates for the abstract, introduction (Problem → Gap → Insight → Contributions), design, evaluation, and related work. - Writing Patterns: Proven argumentation structures such as Gap Analysis (G1–Gn → A1–An), Observation-Driven design, and the "X is better for Y in Z" thesis formula, drawn from published OSDI/SOSP/ASPLOS papers. - Use Case: A PhD student preparing an SOSP submission uses the blueprint to allocate pages, draft the 5-sentence abstract, structure the introduction around 4 numbered contributions, and verify the evaluation follows the three-statement rule before handing off to LaTeX generation. ## Quick Start Ask the assistant to outline an OSDI paper on your system topic using the systems paper blueprint, specifying your target venue and page limit.
