Solution Package Builder
Assemble a submission-ready writer package from final method, result, robustness...
Install
npx skills add zhnnky329/MathModeling-skills --skill solution-package-builder -g -a claude-code -y- Repository
- zhnnky329/MathModeling-skills1.1k
- Category
- Engineering
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Lightabout 681 tokens
- Runs scripts
- No, instructions only
What it does
Assemble a submission-ready writer package from final method, result, robustness, figure, and human-decision artifacts, then freeze approved numerical claims with provenance.
Purpose
Create the writer's single source package and immutable numerical snapshot. Do not manufacture missing judgments or freeze unapproved claims.
Preconditions
rigor_profileissubmission.- Final method explanation, final result analysis, robustness report, and figure plan exist.
- Human method, result, stability, and claim-scope decisions exist in
qx_decisions.jsonl. - Canonical sources are current.
Workflow
- Collect final method structure, result claims, limitations, figures, tables, and decision provenance.
- Draft
results/Qx/reports/qx_solution_package_for_writer.md. - Flag every proposed top-line claim with:
- value and unit;
- canonical source path and location;
- robustness support;
- decision ID for claim scope or rationale;
- confidence/limitation.
- Invoke one final choice card when package sign-off is missing:
- keep;
- downgrade;
- drop.
- Route the human answer to
modeler-decision-loggeraspackage_signoff. - Only after sign-off, generate
results/Qx/reports/frozen_numbers.json. - Verify every numerical package claim resolves to the freeze and every judgment claim resolves to a human decision ID.
Frozen Number Contract
Each entry contains:
{
"claim_id": "q1_main_rmse",
"value": 2.4,
"unit": "units",
"source_file": "results/Q1/experiments/final/metrics/main.json",
"source_locator": "$.rmse",
"frozen_at": "ISO-8601",
"frozen_by_skill": "solution-package-builder",
"decision_id": "q1_package_signoff"
}
Use a source line only for stable text files; use a JSON path, table key, or row/column identifier for structured data.
