scalar-nurture-intakelisted

*[日本語](SKILL.ja.md)* # Scalar Nurture Intake Pre-deal signals in, nurture design out. This skill produces Markdown under `accounts/_nurture/`. It generates no slides. Working directory: the slide-forge root. Sources of truth — this skill redefines none of them: | Concern | Source | |---|---| | The five nurture stages, the product and segment layers, what the sheet leaves unfinished | [`references/scalar/nurture-map.md`](../../references/scalar/nurture-map.md) | | The deal stages a lead is handed to, and the `g1.*` gates | [`references/scalar/stage-io-map.md`](../../references/scalar/stage-io-map.md), [`sales-playbook.md`](../../references/scalar/sales-playbook.md) | | Problem-to-product mapping | [`references/scalar/proposal-map.md`](../../references/scalar/proposal-map.md) | ## Boundaries | Request | Where it goes | |---|---| | Define a segment; design a nurture track; audit content coverage | This skill | | Decide whether a lead is ready for sales | This skill (§6) | | Records for one named customer once a deal exists | `scalar-deal-intake` | | The account ledger and activity-plan deck | `scalar-account-plan` | | Materials for one visit | `scalar-ae-materials` | | Company / product decks (not customer-specific) | `scalar-product-slides` | | Customer-specific proposal | `scalar-proposal-slides` | ## Nurture files hold types, not people A segment is a **pattern**, not a person or a company. Attendance lists, enquiry email and CRM exports contain personal data; the nu