product-partner-brief

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.

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.

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.

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.

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.

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.