Research report · 9 November 2026
Product context: approve the read before the draft
The current Product Marketing instructions offer an optional project-document scan and a persistent shared context file. Copywriting and emails may later read that file, including past Learnings. This is described in source instructions, not observed in a host.
What the source describes
The current Product Marketing selected file displayed version 2.2.0 on 9 November. The older product-marketing-context path returned 404; the present selected file is skills/product-marketing/SKILL.md. The mutable version table lists 15 October for 2.2.0, but neither page pins today's selected-file commit.
If a named local context file exists, the Product Marketing instructions say to read it, summarize version and Changelog, and ask which sections to update. Without one, they offer a conversational route or a recommended auto-draft from README, landing pages, marketing and about copy, metadata, package.json and other documents. The source then asks for product, audience, customer language, competitors, voice, proof and goals, among other fields. Its Brand Voice reference suggests writing, sales, support and review/interview samples and a separate personal-voice profile. These are possible source-described inputs, not material accessed here.
The source says to show the proposed context, seek corrections, save it with version and Changelog, and approve later Learnings rows. Those steps do not themselves authorize the earlier scan, verify accuracy or make a saved assertion suitable for every later task. Copywriting's mutable file displayed 2.3.2 on 9 November and says to read existing context and Learnings before drafting. The tagged emails 2.1.4 selected file has corresponding instructions in the saved full-file comparison; a fresh direct open of that tag returned a cache miss. Its current mutable file displayed corresponding read language, but is not a tag pin.
Read, reuse, review, stop
| Route | Read and reuse boundary | Review and action stop |
|---|---|---|
| One-off local draft: pool-proposed first route | Pass only approved, non-personal brief sections for this task. No ambient file search. Mark absent facts as gaps. | Context owner confirms scope and version; claim, rights and CTA reviewer checks the draft. Do not publish, send or upload from it. |
| Existing shared file: source-described conditional read | Copywriting or emails says to read an existing named file, including Learnings. Approve exact file and sections first or avoid the route; check each learning’s date, evidence and applicability. | Context owner checks Changelog, stale or sensitive entries; copy/email reviewer checks output. No automatic future-task transfer or external action. |
| Product Marketing creation or update: source-described option | Choose an existing-file update, conversational answers, or optional broader project scan. Approve file list, excluded paths, sections and persistent-save/reuse scope before access. | Context owner corrects and approves the document and future Learnings; no account, recipient, publication or send action follows. |
The limits in this table are pool-proposed controls layered on source-described routes. The low-access route was not tested against a real brief, so quality, effort and safety differences are unmeasured.
What remains unknown
No current selected-file SHA/date for Product Marketing or Copywriting, complete package inventory, chosen-host invocation, local product file, personal voice profile, account, customer data, analytics or output test was obtained. A named reference does not prove inclusion in a one-skill archive. The separate emails implementation links can involve credentials, recipients and sending, but their presence is not a required step for a local Markdown draft or permission to act. Host documentation describes possible project paths and permission settings, not an observed run with this material.
Revisit only with an authorized concrete brief and host route, exact intended package bytes, or a material original-source change. A same-case comparison should predefine omissions, provenance, reviewer effort and unauthorized-read/action checks. Do not infer a fifth card or an install recommendation from these source instructions.