scalar-account-planning-sessionlisted

*[日本語](SKILL.ja.md)* # Scalar Account Planning Session Use `references/scalar/workflow-contract.md` for shared safety, Drive, approval, stable-URL, and QA rules. Do not restate or reinterpret stage gates owned by `references/scalar/sales-playbook.md`. APS is an **annual/semi-annual account review**, not the activity plan (`scalar-account-plan`) that gets updated after every visit — the two differ in lifespan and input, so don't mix them. | | Activity plan deck | APS deck (this skill) | |---|---|---| | Purpose | Where things stand now and what to do next | Annual/semi-annual review and executive review | | Update cadence | Every visit | Every APS | | Input | `account.json` (the ledger) | `aps.json` (the ledger + the customer's public information) | | Skill | `scalar-account-plan` | This skill | **A ledger is a prerequisite.** How to build the ledger, verify it, and turn unknowns into actions is covered in [`scalar-account-plan`](../scalar-account-plan/SKILL.md) §1–4. **This skill does not redefine any of that.** The working directory is the slide-forge root. Commands run via `.venv/bin/python`. Page definitions and the judgment criteria for each page are in [references/account-planning-session.md](../../references/account-planning-session.md). Do not redefine either source in this skill. > [references/account-planning-template-plan.md](../../references/account-planning-template-plan.md) > is a **plan document that is not yet implemented**. There is no > `slide-template