product-partner-brief

Generate structured collaboration briefs for peer software vendors from public product artifacts.

3|Updated Jun 30, 2026

Search Tags:#collaboration #integration #roadmap #product-strategy #b2b #partnership

Ready to run

npx skills add https://github.com/henryroxstar/gtm-engine --skill product-partner-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-partner-brief
Source: https://github.com/henryroxstar/gtm-engine/tree/main/plugin/skills/product-partner-brief
Command: npx skills add https://github.com/henryroxstar/gtm-engine --skill product-partner-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of drafting professional, high-stakes collaboration briefs for peer product companies by identifying genuine technical seams and aligning roadmaps without overpromising.

Core Features & Use Cases

Seam Finding: Identifies capabilities that a partner's own documentation or type system names but cannot produce.
Adversarial Verification: Ensures every claim is backed by a public URL and survives adversarial scrutiny.
HTML Companion Generation: Produces a polished, accessible HTML document with CSS-based infographics for positioning and standards alignment.

Quick Start

Use the product-partner-brief skill to draft a collaboration proposal for the company at the provided domain.

Frequently Asked Questions about product-partner-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I draft a product partnership brief that identifies technical integration seams?▼

Draft a product partnership brief by analyzing public product artifacts to validate integration potential, identifying capabilities that a partner's documentation names but cannot produce, and enforcing strict public-source citation gates for every claim.

What is seam finding in B2B software collaboration proposals?▼

Seam finding in B2B software collaboration identifies technical layer boundaries where a peer vendor's type system or documentation names specific capabilities but cannot produce them, revealing genuine integration opportunities for your product roadmap.

How do I generate an HTML document with CSS infographics from a Markdown collaboration brief?▼

Generate an HTML companion document with integrated CSS infographics by processing the structured Markdown collaboration brief, producing polished, accessible positioning and standards alignment visualizations for the partnership proposal.

Can I validate integration potential against a partner's public product documentation without internal API access?▼

Yes, you can validate integration potential by analyzing public product artifacts and enforcing adversarial verification that ensures every technical claim is backed by a public URL, surviving scrutiny without needing internal API access.

Does the partnership brief generation process require dependencies or external libraries?▼

No, the partnership brief generation process requires no external dependencies or libraries, operating independently to analyze public product artifacts and produce both Markdown documentation and responsive HTML companions.

When should I not use an adversarial verification approach for product roadmap alignment?▼

Avoid adversarial verification for product roadmap alignment when internal private documentation is the primary source, as this approach strictly enforces public-source citation gates that require every claim to be backed by a publicly accessible URL.