What problem does it solve?
Producing a strong systems-conference paper often fails at the writing-structure level, where page budgets, paragraph roles, and systems-specific argument patterns are unclear, leading to drafts that feel unfocused or not “OSDI/SOSP/ASPLOS-ready.”
Core Features & Use Cases
- Page allocation for 10–12 page formats across OSDI, SOSP, ASPLOS, NSDI, and EuroSys, with practical section-by-section targets.
- Paragraph-level templates for Abstract, Introduction (problem → gap → insight → contributions), Background/Motivation (definitions + production observations), Design (architecture → module details → alternatives → trade-offs), Implementation, Evaluation (setup → E2E → ablations → scalability), Related Work, and Conclusion.
- Repeatable writing patterns such as Gap Analysis (G1–Gn mapped to evaluation), Observation-Driven design, Contribution lists with section cross-references, and the “X is better for Y in Z” thesis formula.
- Submission workflow guidance including how to draft the blueprint, then delegate final LaTeX/citation verification to a paper-writing workflow.
Quick Start
Use the writing-systems-papers skill to generate a paragraph-by-paragraph structure with page budgets for your target venue and thesis argument.
