home / skills / christopheryeo / claude-skills / new-product

new-product skill

safe

This skill generates enterprise-grade product white papers from existing documentation, delivering structured, evidence-based reports for executive and

npx playbooks add skill christopheryeo/claude-skills --skill new-product

Review the files below or copy the command above to add this skill to your agents.

Files (2)

skill.md

4.0 KB

---
name: new-product
description: Generate comprehensive Enterprise AI Product White Papers using existing product documentation from Google Drive as source material. Use when users request "create a product white paper", "generate a white paper for [product]", or similar requests for enterprise-grade product documentation for SaaS, hardware, or service offerings.
---

# Product White Paper

Generate enterprise-grade product white papers that serve as strategic assets for educating buyers and presenting research-backed solutions to complex business problems.

## Workflow

Follow these steps to generate a product white paper:

1. **Understand the Product:** Clarify which product requires a white paper and identify the target audience (C-suite executives, technical decision-makers, or both)

2. **Gather Source Material:** Search Google Drive for existing product documentation, including:
   - Product specifications and feature descriptions
   - Technical architecture documentation
   - Customer case studies or testimonials
   - Competitive analysis
   - ROI data or success metrics
   - Implementation guides
   - Governance and compliance documentation

3. **Read the Structure Guide:** Load `references/white-paper-essentials.md` to understand the required structure and tone

4. **Generate the White Paper:** Create the white paper following the six-section structure, incorporating information from the gathered source material

5. **Present in Chat:** Output the complete white paper in the chat window formatted in markdown for easy copy-paste

## Search Strategy

When searching Google Drive for source material, use multiple targeted searches:

**For product information:**
```
name contains '[product-name]' and (mimeType = 'application/vnd.google-apps.document' or mimeType = 'application/pdf')
```

**For technical documentation:**
```
fullText contains '[product-name]' and (fullText contains 'architecture' or fullText contains 'technical' or fullText contains 'specification')
```

**For business value content:**
```
fullText contains '[product-name]' and (fullText contains 'ROI' or fullText contains 'value' or fullText contains 'benefit' or fullText contains 'case study')
```

Cast a wide net initially, then narrow based on relevance. Review multiple documents to synthesize comprehensive content.

## White Paper Structure

The white paper must follow this six-section structure (detailed in `references/white-paper-essentials.md`):

1. **Executive Summary** - High-impact summary of strategic and technical takeaways
2. **The Strategic Imperative** - Problem articulation, market context, and business justification
3. **The Solution Blueprint** - Product features, capabilities, and operational benefits
4. **Building Trust** - Governance, assurance, explainability, and risk mitigation
5. **Enterprise Value and ROI** - Multi-dimensional value framework and workforce augmentation
6. **Implementation and Next Steps** - Roadmap, change management, and clear call-to-action

## Tone and Quality Standards

Adhere to these principles:

- **Educational, not promotional:** Establish expertise through depth and research, avoid overt sales language
- **Formal and auditable:** Use engineering/legal-grade formality with verifiable claims
- **Research-backed:** Ground all assertions in evidence from source materials
- **Executive-relevant:** Balance technical depth with strategic business value
- **Conversion-oriented:** Include clear takeaways and actionable next steps

## Output Format

Present the white paper directly in the chat window using markdown formatting:
- Use proper heading hierarchy (# for title, ## for main sections, ### for subsections)
- Bold key terms and concepts for scannability
- Include bullet points for lists of features or benefits
- Maintain professional formatting for easy copy-paste into document editors

## Key References

- **Detailed structure and requirements:** See `references/white-paper-essentials.md` for comprehensive guidance on each section's purpose, required elements, and tone

Overview

This skill generates enterprise-grade product white papers using existing product documentation stored in Google Drive as source material. It produces a six-section, research-backed white paper formatted in Markdown for easy copy-paste into editors. The output is executive-focused, technically rigorous, and conversion-oriented.

How this skill works

I search and synthesize relevant product artifacts from Google Drive (specs, architecture docs, case studies, ROI data, compliance materials). I follow a fixed six-section structure—Executive Summary, Strategic Imperative, Solution Blueprint, Building Trust, Enterprise Value and ROI, and Implementation and Next Steps—and produce a formal, evidence-based narrative. Final output is delivered in Markdown with headings, bolded key terms, and lists for scannability.

When to use it

You need an enterprise white paper to educate buyers or support sales cycles.
You want a research-backed document that combines technical and business perspectives.
You have product artifacts in Google Drive and need them synthesized into a single asset.
You require a formal, auditable document for procurement or governance reviews.
You need a white paper quickly formatted for executive distribution or demand gen.

Best practices

Provide the product name and intended audience (C-suite, technical buyers, or both) upfront.
Grant access to a broad set of Drive documents: specs, architecture, case studies, and ROI metrics.
Confirm the preferred tone and any mandatory compliance/GDPR/security claims before generation.
Review and annotate source docs with priority highlights to improve synthesis accuracy.
Use the produced Markdown as a draft—validate quantitative claims against primary sources before publication.

Example use cases

Create a white paper for a new enterprise SaaS module to support sales enablement and RFP responses.
Synthesize hardware specifications and customer pilots into a governance-ready technical white paper.
Convert implementation guides and ROI analyses into an executive brief for board or investor meetings.
Produce a research-backed document comparing your product’s approach to competitors for marketing campaigns.
Generate a compliance-focused section demonstrating explainability and risk controls for procurement.

FAQ

What source files does the skill use?

I use product specs, architecture docs, case studies, ROI analyses, implementation guides, and governance/compliance documents found in Google Drive.

How long does it take to generate a white paper?

Generation time depends on source volume and complexity; typical drafts are produced within minutes, but review and verification may add time.