wrong-number-triage

Trace wrong on-screen values through form, profile, recipe, and spec-sheet data layers.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill wrong-number-triage-ravenslight2010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrong-number-triage
Source: https://github.com/ravenslight2010/Production-run-calculator/tree/main/.agents/skills/wrong-number-triage
Command: npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill wrong-number-triage-ravenslight2010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a user reports a wrong number on screen ("it says 5.7 but should be 8.25"), the bug could live in any of five data layers, and fixing the wrong layer wastes time. This Skill provides a systematic diagnostic chain to locate the exact layer holding the wrong value before any code is changed. ## Core Features & Use Cases - Layered diagnosis chain: Checks live form/day-state, brand profile pool, recipe pool, saved spec sheets, and the Auto-Fill planner in order, stopping at the first wrong layer. - SQL and file pointers: Provides concrete queries (e.g., inspecting brand_profiles.values jsonb) and file paths (e.g., profileAutofill.ts, storage.ts applySpecImport) for each layer. - Routing to fixes: Directs import/apply bugs to import-bug-investigation, widespread bad rows to data-heal-playbook, and derivation errors to the shared lib/* packages. - Use Case: A floor manager reports the dough batch yield is wrong for one customer. The Skill guides checking the derived form value, then the profile, then the dough recipe's doughballVariants, and finally the saved spec sheet row matching that customer's variantLabel. ## Quick Start Ask the assistant to triage why the web app shows a specific wrong value, stating the expected number and where it appears on screen.

Frequently Asked Questions about wrong-number-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find why a wrong number appears in the web app?

Trace the value through five layers in order: live form state, brand profile pool, recipe pool, saved spec sheet, and Auto-Fill planner. The first layer whose value differs from the expected number is the culprit; downstream layers only display it.

How do I check a brand profile value in the database?

Query the brand_profiles table and extract the field from the values jsonb column, for example selecting (values::jsonb)->>'field' filtered by brand with ilike. Profiles are server-pooled and last-write-wins stamped.

Why is the dough yield wrong for only one customer?

Dough mixing sheets contain many same-named variant rows, so the import may have read the wrong row. Check the saved spec sheet row matching that customer's variantLabel rather than the last row, and verify the recipe's doughballVariants.

When is a wrong number a planner-only bug instead of a data bug?

If stored data in profiles and sheets is correct but the Auto-Fill suggestion is wrong, the bug is in profileAutofill.ts. The planner must mirror the real import's blank-fill rules, so fix the planner without touching stored data.

Should formula errors be fixed in the app code?

No. Derivation formulas live in the shared lib packages such as inventory-math. If the derivation itself is wrong, fix the lib package rather than patching the app inline, so all consumers get the corrected logic.