solution-package-builder
Purpose
Build the writer-facing solution package that integrates all modeling and results work into one coherent, self-contained document. This is the single source of truth that the paper writer uses to draft paper sections for a subquestion.
This skill merges:
- The modeler's final method explanation (what we did and why).
- The programmer's final result analysis (what we got and what it means).
- Planned and generated figures and tables (what visual evidence exists).
- Robustness and sensitivity findings (how stable our conclusions are).
Into one structured package that the paper writer can read and directly translate into paper content without needing to dig through scattered artifacts or guess at missing information.
This skill does not write the actual paper sections, select models, run experiments, generate figures, or perform QA.
This skill does NOT originate the graded sign-off verdict. The package's top-line confidence level and the scope of each top-line claim (which claims survive, which are downgraded, which are dropped) are the single most graded packaging judgments — they get frozen into frozen_numbers.json and propagate verbatim into the paper. The AI may FLAG candidate overclaims and SUGGEST a confidence level, both explicitly labeled as ai_suggestion. It must NOT decide keep/downgrade/drop for any claim, and it must NOT assign the package's confidence verdict. Those are the human's to render at the gate (see Workflow step 7.4 / Gate G4.5 package sign-off). The method-selection narrative in the package is TRANSCRIBED from the decision log with decision_id provenance — it is never re-authored here.
When to use
Use this skill: