What problem does it solve? Product managers often need to turn already-confirmed product judgments into polished direction memos, positioning statements, product introductions, feature lists, one-pagers, or executive briefing materials, but writing these from scratch is slow and prone to vague, slogan-heavy language. This Skill turns confirmed product decisions into structured, evidence-grounded Markdown documents under docs/deliverables/. ## Core Features & Use Cases - Multiple document types: Produces product direction memos, positioning statements, product introductions, feature lists, advantage statements, one-pagers, and decision/briefing materials, each with a fit-for-purpose structure. - Evidence-grounded writing: Reads the accepted proposal contract, PRODUCT.md, PRODUCT-STATE.md, and module specs so every key judgment traces back to a source, with unverified claims marked as assumptions. - Boundary enforcement: Redirects PRD and functional spec requests to /pmai-spec-writing and unresolved product direction questions to /pmai-proposal, keeping this Skill focused on expression rather than judgment. - Use Case: After confirming a product direction with stakeholders, ask for a one-page executive briefing; the Skill reads the current product baseline, drafts a judgment-first document with trade-offs and success metrics, writes it to docs/deliverables/, and updates the deliverables index. ## Quick Start Ask the assistant to write a product introduction one-pager for your confirmed product direction and save it to docs/deliverables/.
