What problem does it solve?
Writing a strong systems conference paper often fails at the “paragraph level” because authors lack venue-specific page budgeting, reusable paragraph roles, and consistent writing patterns.
Core Features & Use Cases
- Venue-ready page allocation for 10–12 page systems papers (OSDI/SOSP/ASPLOS/NSDI/EuroSys) so every section fits the camera-ready constraints.
- Paragraph-level blueprints for the abstract, introduction, background, design, implementation, evaluation, related work, and conclusion with explicit role templates.
- Writing patterns that drive stronger structure such as Gap Analysis, Observation-Driven design, Contribution Lists, and the “X is better for Y in Z” thesis formula.
- Use case: You need to convert a rough systems idea into a submission-ready outline where each paragraph has a job, evidence expectations, and a measurable evaluation plan.
Quick Start
Use this skill when you want fine-grained systems-paper structure guidance for an OSDI, SOSP, ASPLOS, NSDI, or EuroSys submission.