Use for the "Problem Statement" step in a NeurIPS paper workflow when you need paragraph output for the Introduction stage from verified inputs. Best for when refining or drafting the introduction portion of a neurips-style paper; when you need a reusable artifact rather than a one-off paragraph rewrite; not for inventing unsupported experiments, citations, proofs, or contributions.
Original id: 02_04_problem_statement_skill
Section: Introduction
Layer: section
Category: introduction
Produce a reusable problem statement module for Introduction within a NeurIPS paper workflow, with explicit boundaries, evidence discipline, and handoff-ready structure.
Required inputs:
paper_blueprint (required): Verified paper-level question, answer, storyline, contributions, and target sections.contribution_list (required): Stable list of contributions already accepted by the authors as in-scope and evidence-backed.claim_evidence_map (required): Claim-to-evidence alignment table used to prevent unsupported statements and novelty inflation.section_fact_sheet (required): Verified notes for Introduction with missing items clearly marked.Optional inputs:
terminology_registry (optional): Canonical terms, symbols, and disallowed variants for consistency control.current_draft_context (optional): Existing local draft text or outline to revise, compress, or audit.venue_constraints (optional): Page limit, formatting rules, length pressure, or author preference on tone.paragraphobjective_interpretation, main_output, risk_flags, handoff_notesreviewer-friendly / Englishreferences/spec.yaml.Core hard rules:
Section-specific checks:
Revision policy:
Reasoning focus:
Self-checklist:
Upstream skills:
00_01_paper_blueprint_skill00_02_storyline_architect_skill00_03_contribution_extractor_skill00_04_claim_evidence_alignment_skill00_06_terminology_notation_registry_skill02_03_intro_hook_skillDownstream handoff:
02_05_method_teaser_skill