hearing-sheetlisted

*[日本語](SKILL.ja.md)* # Hearing Sheet I/O Read `references/hearing-kit.md` first — the record, the merge rule, the customer filter and the command list are all there, and **this skill does not restate them**. This file owns only the workflow and the decisions. Working directory: the slide-forge root. Run everything with `.venv/bin/python`. ## Boundaries | Request | Where it goes | |---|---| | A hearing sheet in md / xlsx / Google Spreadsheet, in either direction | This skill | | What is still unconfirmed, and who can answer it | This skill (`gaps`) | | Slides that ask the open questions | `hearing-slides` | | Minutes, email or a CRM export → the record | `scalar-deal-intake` | | Whether the product fits, and which edition | `templates/sales/products/<product>.ja.md` (a person judges; only the verdict lands here) | | Gate and BANT judgements | `references/scalar/sales-playbook.md` | | A quote or a BOM spreadsheet | `spreadsheets` | | The proposal deck | `scalar-proposal-slides` | ## Step 1: Find or start the record ```bash ls accounts/<AE>/<customer>/stages/hearing.json ``` If it is missing, start it from the blank form — and from the product addendum when a product is already in play: ```bash .venv/bin/python scripts/hearing/hearing_sheet.py init \ templates/sales/hearing-sheet.ja.md \ --out accounts/<AE>/<customer>/stages/hearing.json --product scalar ``` **Do not start a second record for the same deal.** One deal, one `hearing.json`, one Google Spreadsheet