Update to Icanpreneur

{
  "description": "Turn a Buyer Persona into go-to-market assets in Icanpreneur: positioning and messaging, a landing page, a sales deck, and a webpage or Google Slides preview. Use when the user wants positioning, messaging, landing-page copy, a sales or pitch deck, wants to edit or refine those, regenerate them, or get a preview link. Load `icanpreneur` first. Do not use for generic copywriting, building a custom website, or an unrelated presentation. Covers the generation order, which ID goes where, editing without regenerating, previews, and what the assets can and cannot claim.",
  "included_files": [
    {
      "relative_path": "references/editing-and-previews.md",
      "size_in_bytes": 2695
    }
  ],
  "name": "icanpreneur-gtm-assets",
  "skill_md_contents": "---\r\nname: icanpreneur-gtm-assets\r\ndescription: 'Turn a Buyer Persona into go-to-market assets in Icanpreneur: positioning and messaging, a landing page, a sales deck, and a webpage or Google Slides preview. Use when the user wants positioning, messaging, landing-page copy, a sales or pitch deck, wants to edit or refine those, regenerate them, or get a preview link. Load `icanpreneur` first. Do not use for generic copywriting, building a custom website, or an unrelated presentation. Covers the generation order, which ID goes where, editing without regenerating, previews, and what the assets can and cannot claim.'\r\n---\r\n\r\n# Positioning, landing page, sales deck and previews\r\n\r\nLoad [icanpreneur](../icanpreneur/SKILL.md) first; its rules apply.\r\n\r\n```\r\nBuyer Persona → Positioning and messaging → Landing page ─┐\r\n                                          └→ Sales deck ──┴→ Preview (webpage / Google Slides)\r\n```\r\n\r\n- Positioning needs a persona (`generate_positioning_and_messaging`, with `buyerPersonaId`).\r\n- A landing page or deck needs a **positioning document** (`generate_landing_page`, `generate_sales_deck`, with `positioningDocumentId`).\r\n- A preview needs a landing page or deck (`generate_buyer_persona_document_preview`, with `buyerPersonaDocumentId`). Positioning has no preview.\r\n\r\nEvery document is one shared resource. Its `id` is the `buyerPersonaDocumentId` for read, update, delete and preview, and the `positioningDocumentId` when it is a `PositioningAndMessaging` document. It is not the content `documentId`. Never pass a persona ID to the page or deck generators.\r\n\r\nDone means the documents asked for are `ready` with `error: false`, requested previews are `ready` with `error: false` and a link, and the user knows what evidence the assets rest on. Generate only what was asked: \"positioning\" is not a request for a page and a deck.\r\n\r\n## 1. Check the starting point\r\n\r\n1. Find the workspace and persona. No persona → `icanpreneur-build-research`.\r\n2. Positioning generation requires `status: Complete` and a nonempty `description` (`get_buyer_persona`). This applies to existing personas too: Pending/Error is rejected even when fields from an older profile remain. Wait briefly or report the block; there is no tool to select a previous completed version. An empty Complete persona is not ready, and Complete does not prove recent interviews are included.\r\n3. Count the real and synthetic interviews in the source research (`icanpreneur` → `references/evidence.md`). If mostly synthetic, say in the hand-over that the assets express a hypothesis. This is disclosure, not an approval step.\r\n4. `list_buyer_persona_documents` shows what exists. Each generation makes a new document; if it is unclear whether to reuse the existing positioning, ask.\r\n5. Use the workspace or research language unless asked.\r\n\r\n## 2. Generate\r\n\r\nThese calls are billable. Say which steps use credits, then run the chain the user asked for without stopping at each step.\r\n\r\n1. Positioning; wait for `ready: true` and `error: false` (`get_buyer_persona_document`; `text` can be null while saved content is unavailable). On `error: true`, report it. Never write the positioning, page or deck yourself in place of the generator.\r\n2. Pause to show the positioning only if the user asked to review or refine it first. Otherwise continue. Pages and decks capture their source when generated, so the time to change the positioning is before they are built.\r\n3. Landing page and/or deck from the positioning's `id`. Wait for `ready`.\r\n4. A request for a preview is the authorization. Do not ask again because it is billable.\r\n\r\n**Before editing any generated text, or generating or refreshing a preview, read [references/editing-and-previews.md](references/editing-and-previews.md).** Prefer editing the Markdown over regenerating.\r\n\r\n## 3. Review after new evidence\r\n\r\nWhen new interviews have changed the persona, or the user asks whether the assets still fit, compare before regenerating. Check the positioning against the persona on five points: core problem, desired outcomes, perceived barriers, decision criteria and customer language. Say where they differ. Regenerate positioning only if it no longer reflects the latest buyer understanding and the user asks. A Canvas or persona change alone does not show an asset must be regenerated. Regenerate pages and decks only after the positioning is settled.\r\n\r\nGenerated assets are strong first drafts, written with the customer as the hero and speaking to their problem, outcomes and reasons to act. Keep that structure when editing, and tell the user to refine them in their own voice and test them with target buyers.\r\n\r\n## 4. Hand over\r\n\r\nReport the documents (name, type, ready), preview links, the persona and evidence line, and any placeholders left. Offer to save the positioning decisions as a note. `export_buyer_persona` gives the persona as Markdown for a handover. Deleting: follow `icanpreneur` and the reference.\r\n\r\n## Mistakes to avoid\r\n\r\n- Regenerating to make a small change, or regenerating a deck preview repeatedly (each is a new presentation).\r\n- Sending `text` for only part of a document.\r\n- Adding proof points no tool returned.\r\n- Pausing for approval at each billable step of a chain the user asked for.\r\n"
}