scalar-account-planlisted

*[日本語](SKILL.ja.md)* # Scalar Account Plan Use `references/scalar/workflow-contract.md` for shared safety, Drive, approval, and QA rules. `references/scalar/sales-playbook.md` remains the only source for phases, gates, and checkpoint definitions. One ledger per customer. **The ledger is the single source of truth**; the deck is just a rendering of it. Append to the ledger after every visit, and refresh the deck at the same URL. Two kinds of deck come out of the ledger. They have different lifespans and inputs, so don't mix them. **This skill covers the left one.** | | Activity plan deck (§5) | APS deck | |---|---|---| | Purpose | Where things stand now and what's next | Annual/half-year review and executive review | | Updated | After every visit | At each APS | | Input | `account.json` (the ledger) | `aps.json` (the ledger + the customer's public information) | | Skill | **This skill** | `scalar-account-planning-session` | Working directory: the slide-forge root. Run commands with `.venv/bin/python`. ## Boundaries | Request | Where it goes | |---|---| | Create / append to the activity plan, or answer about status | This skill (§5) | | Build materials for an Account Planning Session | `scalar-account-planning-session` | | Build a full set of materials for one visit | `scalar-ae-materials` | | Organise minutes / email into per-stage records | `scalar-deal-intake` | | Draw the stakeholder map / discovery map itself | `b2b-account-maps` | | Formal customer-facing proposal