Context Slice Content Type Recognition
Match user intent to the appropriate guide:
| User says | Content Type | Guide |
|---|---|---|
| "PRD", "product requirements", "feature spec", "requirements doc" | PRD | PRD Writing Guide |
| "one-pager", "feature brief", "quick spec", "brief", "summary doc" | Brief | Brief Writing Guide |
| "changelog", "release notes", "what's new", "version notes" | Changelog | Changelog Writing Guide |
| "FAQ", "go-to-market FAQ", "internal FAQ", "sales FAQ" | GTM FAQ | GTM Content Guide |
| "value prop", "value proposition", "one-liner", "tagline" | Value Proposition | GTM Content Guide |
| "pitch deck", "deck outline", "stakeholder presentation" | Pitch Deck | Pitch Deck Guide |
Task Routing
For complex content types with many required inputs, use the dedicated task:
| Content Type | Route To |
|---|---|
| PRD / Feature Spec |  Create PRD |
| One-Pager / Feature Brief | Create Brief |
| Pitch Deck | Create Pitch Deck Outline |
| Changelog / Release Notes | Create Changelog |
All other content types (FAQs, value props) use slice guidance directly.
Choosing between PRD and Brief: If the user asks for "quick" documentation, stakeholder alignment, or early-stage exploration, suggest a brief. If they need engineering handoff or detailed acceptance criteria, use a PRD. When unsure, ask: "Do you need a quick one-pager for alignment, or a full PRD for engineering handoff?"
Product Context Profile
Check 
Product Context Profile before generating any content. If it exists, use its context:
- Company/product info → Use for background sections, positioning
- User personas → Use for user stories, problem statements
- Competitors → Use for differentiation in value props, pitch decks
If the user shares company, product, or user info not already in the profile, offer to save it:
"Want me to save this to your product profile so it's available for future content?"
Gathering Context
Before generating content, ensure you have the required inputs. Each guide specifies what context is needed. If missing, check Product Context Profile first, then ask the user.
Common context patterns:
- Feature-specific: Feature name, problem being solved, proposed solution
- User-specific: Target persona, pain points, goals
- Release-specific: Version number, release date, changes list
- Audience-specific: Who will read this (engineering, users, leadership)
Output Behavior
- Identify content type from user request
- Load the relevant guide slice
- Gather any missing required context
- Generate content following the guide's structure
- Output directly as ready-to-use content (not wrapped in explanation)
For documents (PRDs, pitch decks), use markdown formatting.
For changelogs, use the user's preferred format or default to markdown.
For value props, output multiple versions for different audiences.
When Ambiguous
If the request could match multiple content types, ask:
"Should this be a [most likely type] or would [alternative] work better?"
First-Run Experience
When Product Context Profile doesn't exist or is empty:
- Acknowledge this is their first time using the skill for this product
- Briefly explain the benefit: "A product profile helps me generate more consistent content—I'll reference your personas, competitors, and positioning across all PRDs, changelogs, and decks."
- Offer a choice: create one now OR proceed without and offer after the first task
- Don't block content creation—the profile is helpful but not required
Example prompt: "I don't see a product profile yet. Want me to help you set one up (takes ~5 minutes), or should we jump into the [content type] and I'll offer to save context afterward?"