Write comprehensive blog post:

Topic: [YOUR TOPIC]
Target audience: [SPECIFIC AUDIENCE]
Word count: [800/1200/1500]
Goal: [Educate/Persuade/Entertain]

Structure:
- Compelling headline (8-12 words, includes keyword)
- Hook opening (problem or surprising statistic)
- 3-5 main sections with subheadings
- Practical examples in each section
- Actionable takeaways
- Strong conclusion with CTA

Tone: [Professional/Casual/Authoritative]
SEO keyword: [PRIMARY KEYWORD]

Write email for:

Type: [Sales/Newsletter/Announcement/Follow-up]
Recipient: [Job title/industry]
Goal: [Specific action you want them to take]

Context:
- Relationship: [Cold outreach/Existing customer/Prospect]
- Previous interaction: [If any]
- Why now: [Urgency or relevance]

Email elements:
- Subject line (under 50 characters, compelling)
- Preview text (complements subject)
- Opening (personalized, contextual)
- Body (3-4 short paragraphs max)
- Clear CTA (specific, actionable)
- Signature

Tone: [Professional yet friendly/Direct/Consultative]
Length: [Short (under 150 words)/Medium (150-250)/Long]

Repurpose this content into [TARGET FORMAT]:

Original content: [PASTE CONTENT OR URL]
Original format: [Blog post/Video transcript/Podcast/Presentation]

Transform into: [LinkedIn post/Twitter thread/Email newsletter/Instagram caption]

Requirements:
- Maintain core message but adapt to platform norms
- [Platform] optimal length: [SPECIFY]
- Include platform-specific elements: [Hashtags/Mentions/@tags]

Edit this text for:

Original text: [PASTE TEXT]

Focus areas:
1. Grammar and spelling errors
2. Clarity (remove ambiguity, simplify complex sentences)
3. Conciseness (eliminate redundancy, tighten prose)
4. Tone consistency (ensure matches [DESIRED TONE])
5. Flow (improve transitions between ideas)

Specific requests:
- Keep word count under [NUMBER]
- Maintain [Formal/Casual] voice
- Preserve technical terms: [LIST IF ANY]

Generate 20 headline options for:

Content topic: [YOUR TOPIC]
Content type: [Blog post/Video/Podcast/Email]
Target audience: [SPECIFIC AUDIENCE]

Headline styles (generate mix):
- How-to (practical guidance)
- Numbered list (e.g., "7 Ways to...")
- Question (intriguing, answerable)
- Benefit-driven (clear value)
- Contrarian (challenges assumption)

Requirements:
- Include keyword: [PRIMARY KEYWORD]
- Length: [Under 60 characters for SEO/Under 100 for email]
- Emotional trigger: [Curiosity/Fear/Desire/Urgency]

Create engaging social media post:

Platform: [LinkedIn/Twitter/Instagram/Facebook]
Topic: [YOUR TOPIC]
Goal: [Awareness/Engagement/Traffic/Conversion]

Post elements:
- Hook (first sentence must stop scroll)
- Value delivery (insight, tip, story)
- Call-to-action (comment, share, click link)
- [Hashtags if Instagram: 5-10 relevant]
- [Mentions if applicable: @username]

Length: 
- LinkedIn: 150-300 words (longer OK if valuable)
- Twitter: 200-250 characters (leave room for retweets)
- Instagram: 125-150 words

Tone: [Professional/Inspirational/Educational/Entertaining]

Write compelling product description:

Product: [PRODUCT NAME]
Category: [PRODUCT CATEGORY]
Target customer: [DEMOGRAPHIC/PSYCHOGRAPHIC]
Price point: [BUDGET/MID-RANGE/PREMIUM]

Product details:
- Key features: [LIST 3-5]
- Benefits: [How it solves customer problems]
- Unique selling points: [What makes it different]
- Technical specs: [IF RELEVANT]

Description requirements:
- Length: [100/250/500 words]
- Focus on benefits, not just features
- Address customer pain points
- Include sensory details (how it feels, looks, performs)
- SEO keywords: [LIST]

Format:
- Compelling headline
- Opening hook (emotional connection)
- Feature/benefit bullets
- Social proof mention (if available)
- Clear CTA

Tone: [Persuasive yet authentic/Luxury/Technical/Friendly]

Write script for:

Format: [YouTube video/Podcast episode/Webinar/Presentation]
Length: [5 min/10 min/30 min/60 min]
Topic: [YOUR TOPIC]
Audience: [SPECIFIC AUDIENCE]

Script structure:
- Hook (first 10 seconds, grab attention)
- Intro (who you are, what they'll learn, why it matters)
- Main content (3-5 key points with examples)
- Transitions (smooth flow between sections)
- Engagement prompts (questions, calls for interaction)
- Conclusion (summary, CTA)

Requirements:
- Conversational tone (written to be spoken)
- Natural pacing (indicate pauses, emphasis)
- Visual cues [if video: what's on screen]

Write press release:

Announcement: [WHAT YOU'RE ANNOUNCING]
Company: [COMPANY NAME]
Industry: [INDUSTRY]
Release date: [DATE]

Press release structure:
- Compelling headline (newsworthy angle)
- Dateline (City, State, Date)
- Lead paragraph (Who, What, When, Where, Why)
- Quote from company executive (CEO, founder)
- Supporting details (2-3 paragraphs)
- Quote from customer or partner (if applicable)
- Company boilerplate (About [Company]

Write customer success case study:

Customer: [COMPANY/PERSON NAME]
Industry: [INDUSTRY]
Challenge: [PROBLEM THEY FACED]
Solution: [YOUR PRODUCT/SERVICE]
Results: [MEASURABLE OUTCOMES]

Create email newsletter:

Newsletter name: [NAME]
Frequency: [Weekly/Monthly]
Target audience: [SUBSCRIBER DEMOGRAPHIC]
Primary goal: [Educate/Entertain/Sell/Update]

Newsletter sections:
- Subject line (compelling, under 50 chars)
- Preview text (complements subject, 40-100 chars)
- Header/greeting (personalized, sets tone)
- Main content (1-3 articles/updates)
- Featured item (highlight, visual)
- Community/social (engagement element)
- Footer (unsubscribe, contact, social links)

Content balance:
- [X]% educational/valuable content
- [X]% promotional content
- [X]% community/personal

Tone: [Friendly expert/Professional/Conversational]
Length: [Under 500 words/500-1000/1000+]

Write testimonial request message:

Recipient: [CUSTOMER NAME]
Product/Service: [WHAT THEY USED]
Relationship: [HOW LONG CUSTOMER]
Results they achieved: [IF KNOWN]

Message elements:
- Personalized greeting
- Context (reference their experience)
- Specific request (written testimonial, video, both)
- Make it easy (provide guiding questions)
- Explain use (where testimonial will appear)
- Incentive (if offering: discount, gift, donation)
- Thank you and deadline (reasonable timeframe)

Guiding questions to include:
1. What problem were you trying to solve?
2. Why did you choose us?
3. What results did you achieve?
4. What would you tell someone considering us?

Tone: Appreciative, not demanding
Length: Short and respectful (under 200 words)

Follow-up plan:
- If no response: Gentle reminder after [X days]

Create FAQ section for:

Topic: [YOUR TOPIC/PRODUCT/SERVICE]
Audience: [WHO'S ASKING]
Context: [Website/Documentation/Onboarding]

Generate [10/15/20] questions covering:
- Common objections (price, complexity, fit)
- Technical questions (how it works, specs)
- Comparison questions (vs alternatives)
- Process questions (how to start, timeline)
- Support questions (help, troubleshooting)

For each FAQ:
- Question (natural language, how customer asks)
- Answer (clear, concise, helpful)
  * If technical: explain simply
  * If pricing: be transparent
  * If process: provide steps
- Links (to relevant resources if helpful)

Requirements:
- Answer length: 50-150 words each
- Tone: Helpful, not defensive
- Include: specific details, avoid vague responses
- Anticipate follow-ups (link to related FAQs)

Organize by:
[Category-based/Chronological/By user type]

Create white paper outline:

Topic: [INDUSTRY PROBLEM/TREND]
Target audience: [DECISION-MAKERS/TECHNICAL/EXECUTIVES]
Goal: [Thought leadership/Lead generation/Education]
Length: [8-12 pages/15-20 pages/20+ pages]

Write YouTube video description:

Video title: [VIDEO TITLE]
Video topic: [MAIN TOPIC]
Video length: [MINUTES]
Target keywords: [SEO KEYWORDS]

Write ad copy for:

Platform: [Google Ads/Facebook/Instagram/LinkedIn]
Product/Service: [WHAT YOU'RE SELLING]
Target audience: [DEMOGRAPHICS/INTERESTS/BEHAVIORS]
Campaign goal: [Awareness/Consideration/Conversion]
Budget: [DAILY/MONTHLY SPEND]

Ad format requirements:
[Google Search Ads]
- 3 headlines (30 chars each)
- 2 descriptions (90 chars each)
- Display URL
- Ad extensions (sitelinks, callouts)

[Facebook/Instagram Feed]
- Primary text (125 chars)
- Headline (40 chars)
- Description (30 chars)
- Call-to-action button text

[LinkedIn Sponsored]
- Introductory text (150 chars)
- Headline (70 chars)
- Description (100 chars)

Ad copy principles:
- Lead with benefit, not feature
- Address pain point or desire
- Include specific offer/value prop
- Create urgency (if appropriate)
- Clear, actionable CTA

Generate: 5 variations for A/B testing
Each variation testing: [Different angle/hook/offer]

Write landing page copy for:

Product/Service: [WHAT YOU'RE SELLING]
Target audience: [SPECIFIC DEMOGRAPHIC]
Traffic source: [Google Ads/Social/Email/Organic]
Goal: [Sign up/Purchase/Demo request/Download]

Landing page sections:
1. Hero Section
   - Headline (benefit-driven, clear value)
   - Subheadline (supporting detail)
   - Hero image/video suggestion
   - Primary CTA button

2. Problem Statement
   - Pain points (3-4 bullets)
   - Current frustrations
   - Cost of status quo

3. Solution (Your Product)
   - How it works (3-step process visual)
   - Key features (with benefits)
   - Differentiation (why choose us)

4. Social Proof
   - Customer logos
   - Testimonials (2-3 specific quotes)
   - Stats/metrics (if available)

5. Features/Benefits
   - 3-column layout
   - Icon + headline + 2-sentence description each

6. Objection Handling
   - FAQ (5-7 questions)
   - Trust signals (security, guarantee)

7. Final CTA
   - Restate value
   - Low-friction offer
   - Urgency element (if appropriate)

Tone: [Conversational/Professional/Urgent]

Write podcast show notes:

Episode title: [EPISODE TITLE]
Episode number: [NUMBER]
Guest: [GUEST NAME if applicable]
Duration: [MINUTES]
Release date: [DATE]

Show notes structure:
- Episode summary (2-3 sentences, compelling)
- Guest bio (if interview, 100 words)
- Key topics covered (bulleted list)
- Timestamps (major segments)
- Resources mentioned (books, tools, links)
- Quotes (3-5 memorable soundbites from episode)
- Where to listen (platform links)
- Next episode teaser
- Call-to-action (subscribe, review, share)

Requirements:
- SEO-friendly (include relevant keywords)
- Scannable (use formatting: bold, bullets)
- Length: 400-600 words
- Include: episode number, date, guest name in meta

Timestamp format:
[2:15] Introduction to [Topic]
[8:30] Deep dive into [Specific Point]
[15:45] Actionable advice on [Topic]

Write professional bio/resume section:

Format: [Resume objective/Executive summary/LinkedIn About/Speaker bio]
Person: [NAME]
Industry: [INDUSTRY]
Career level: [Entry/Mid/Senior/Executive]
Target role/audience: [WHO'S READING]

Information to include:
- Current role and company
- Years of experience
- Key expertise areas (3-5)
- Notable achievements (quantified)
- Education/certifications (if relevant)
- Unique value proposition

Bio variations by length:
- Short (50-75 words): Elevator pitch version
- Medium (150-200 words): LinkedIn/website
- Long (300-400 words): Speaking/conference bio

Resume sections:
- Professional summary (3-4 sentences)
- Core competencies (skill bullets)
- Work experience (bullets focused on achievements)

Requirements:
- Third person for bio, first person for summary
- Action verbs (led, increased, developed)
- Metrics where possible (%, $, scale)
- Tone: [Confident yet humble/Authoritative/Approachable]

Ghostwrite in the voice of:

Person: [CLIENT NAME]
Platform: [LinkedIn/Blog/Twitter/Newsletter]
Topic: [SUBJECT MATTER]
Audience: [TARGET READERS]

Voice characteristics:
- Tone: [Analytical/Conversational/Provocative/Supportive]
- Sentence structure: [Short and punchy/Longer, complex/Mixed]
- Vocabulary level: [Accessible/Technical/Sophisticated]
- Personality traits: [Humble/Confident/Humorous/Serious]
- Recurring themes: [TOPICS THEY CARE ABOUT]

Writing samples to mimic:
[PASTE 2-3 EXAMPLES OF THEIR WRITING]

Content requirements:
- Length: [WORD COUNT]
- Format: [Essay/Thread/Listicle/Story]

Review this code for:

Language: [PYTHON/JAVASCRIPT/ETC]
Context: [WHAT CODE DOES]
Focus areas:
1. Bugs and errors
2. Performance optimization
3. Security vulnerabilities
4. Code readability and maintainability
5. Best practices adherence

Code to review:
[PASTE CODE]

Provide:
- Issues found (categorize by severity: Critical/High/Medium/Low)
- Specific line references
- Explanation of each issue
- Recommended fixes (code examples)
- General observations

Review framework:
- Functionality: Does it work correctly?
- Performance: Are there efficiency improvements?
- Security: Any vulnerabilities or unsafe practices?
- Maintainability: Is it readable and well-structured?
- Style: Does it follow [LANGUAGE]

Help debug this code:

Language: [LANGUAGE]
Error message: [PASTE ERROR]
Expected behavior: [WHAT SHOULD HAPPEN]
Actual behavior: [WHAT'S HAPPENING]

Code:
[PASTE CODE]

Context:
- Framework/libraries: [IF ANY]
- Environment: [DEVELOPMENT/PRODUCTION]
- When error occurs: [SPECIFIC TRIGGER]
- Recent changes: [WHAT CHANGED BEFORE ERROR]

Refactor this code for:

Current code:
[PASTE CODE]

Refactoring goals (prioritize):
- [ ] Improve readability
- [ ] Enhance performance
- [ ] Reduce complexity
- [ ] Follow [STYLE GUIDE] conventions
- [ ] Remove code duplication
- [ ] Better error handling
- [ ] Improved testability

Constraints:
- Maintain existing functionality (exact same behavior)
- [Language]: [VERSION]
- [Framework]: [IF APPLICABLE]
- Must be backward compatible: [YES/NO]

Provide:
- Refactored code (complete, ready to use)
- Explanation of changes made
- Before/after comparison (key improvements)
- Potential risks or trade-offs
- Testing recommendations

Focus on:
[SPECIFIC AREAS OF CONCERN]

Generate documentation for:

Code: [PASTE CODE OR FUNCTION]
Language: [LANGUAGE]
Documentation type: [API docs/README/Inline comments/User guide]

Documentation requirements:

[For Functions/Methods]
- Purpose (what it does)
- Parameters (type, description, default values, required/optional)
- Return value (type, description)
- Exceptions (what errors can be raised)
- Examples (usage code snippets)
- Notes (edge cases, performance considerations)

[For Classes]
- Class purpose and responsibility
- Constructor parameters
- Public methods (document each)
- Properties/attributes
- Usage examples
- Inheritance information

[For API Endpoints]
- Endpoint path and HTTP method
- Request parameters (query, body, headers)
- Request/response examples (JSON)
- Status codes and error responses
- Authentication requirements
- Rate limits (if applicable)

Format: [Markdown/Docstring/JSDoc/Javadoc]

Implement algorithm for:

Problem: [DESCRIBE PROBLEM]
Input: [DATA STRUCTURE AND FORMAT]
Output: [EXPECTED RESULT]
Constraints:
- Time complexity: [TARGET BIG-O]
- Space complexity: [TARGET BIG-O]
- Language: [PREFERRED LANGUAGE]

Requirements:
- Efficient implementation
- Handle edge cases (empty input, single element, duplicates, etc.)
- Input validation
- Clear variable names
- Comments explaining complex logic
- Example usage

If multiple approaches exist:
- Provide [NUMBER]

Create API integration for:

API: [API NAME AND ENDPOINT]
Purpose: [WHAT YOU'RE INTEGRATING]
Language: [YOUR LANGUAGE]

API details:
- Base URL: [URL]
- Authentication: [API key/OAuth/Bearer token]
- Rate limits: [IF KNOWN]
- Documentation: [LINK IF AVAILABLE]

Integration requirements:
- Create wrapper class/module
- Handle authentication
- Implement error handling (retries, timeouts)
- Rate limit management
- Request/response logging
- Type hints/interfaces (if applicable)

Specific endpoints needed:
[LIST ENDPOINTS YOU NEED TO CALL]

Optimize this database query:

Current query:
[PASTE SQL/QUERY]

Database: [PostgreSQL/MySQL/MongoDB/etc]
Context:
- Table sizes: [APPROXIMATE ROWS]
- Current performance: [EXECUTION TIME]
- Target performance: [DESIRED TIME]
- Frequency: [HOW OFTEN RUNS]

Generate unit tests for:

Code to test:
[PASTE CODE]

Testing framework: [pytest/Jest/JUnit/etc]
Coverage goal: [80%/90%/100%]

Test requirements:
- Happy path tests (normal inputs)
- Edge cases (empty, null, boundary values)
- Error conditions (invalid inputs, exceptions)
- Integration points (if applicable)

For each test:
- Descriptive test name
- Arrange (setup)
- Act (execute)
- Assert (verify)
- Cleanup (if needed)

Testing patterns:
- Mocking (for external dependencies)
- Fixtures (reusable test data)
- Parametrized tests (multiple inputs)

Include:
- Test file structure
- Setup/teardown methods
- Mock examples (for database, API calls, etc.)
- Assertion best practices
- Coverage report guidance

Generate [NUMBER]

Migrate code from [SOURCE] to [TARGET]:

Source code:
[PASTE CODE]

Source: [LANGUAGE/FRAMEWORK VERSION]
Target: [LANGUAGE/FRAMEWORK VERSION]

Design software architecture for:

Project: [PROJECT NAME]
Purpose: [WHAT SYSTEM DOES]
Scale: [Expected users/data volume]
Technology stack: [PREFERRED TECH]

Requirements:
- Functional requirements: [LIST]
- Non-functional requirements: [Performance, security, scalability]
- Constraints: [Budget, timeline, team size]

Architecture components:
- High-level system diagram
- Component breakdown (modules, services)
- Data flow (how information moves)
- Technology choices (with justification)
- API design (endpoints, data structures)
- Database schema (tables, relationships)
- Security considerations
- Scalability plan

Deliverables:
- Architecture diagram (description, ASCII, or structured format)
- Component descriptions (purpose, responsibilities)
- Interface definitions (APIs, contracts)
- Technology recommendations
- Implementation phases (order, priorities)
- Risk assessment (potential issues, mitigations)

Format: [Markdown/Structured doc/Diagrams]

Create reusable [COMPONENT TYPE] component:

Framework: [React/Vue/Angular/Svelte]
Component: [SPECIFIC COMPONENT]
Use cases: [WHERE IT WILL BE USED]

Component requirements:
- Props/inputs: [LIST WHAT COMPONENT RECEIVES]
- State management: [LOCAL STATE/GLOBAL STATE]
- Events/outputs: [WHAT COMPONENT EMITS]
- Styling: [CSS/Styled-components/Tailwind/etc]
- Accessibility: WCAG 2.1 AA compliance
- Responsiveness: Mobile-first

Features:
[LIST SPECIFIC FEATURES]

Provide:
- Component code (complete, production-ready)
- PropTypes/TypeScript interfaces
- Usage examples (3-5 scenarios)
- Styling (with variants if applicable)
- Test cases
- Accessibility notes (keyboard nav, ARIA labels)
- Documentation (props, events, examples)

Follow: [STYLE GUIDE IF ANY]
Design system: [IF APPLICABLE]

Create API endpoint:

Framework: [Express/Flask/Django/FastAPI/etc]
Endpoint: [HTTP METHOD] [PATH]
Purpose: [WHAT ENDPOINT DOES]

Endpoint specifications:
- Authentication: [Required/Optional/None]
- Authorization: [ROLE-BASED/PERMISSIONS]
- Request:
  * Path parameters: [IF ANY]
  * Query parameters: [IF ANY]
  * Request body: [STRUCTURE]
  * Headers: [REQUIRED HEADERS]
- Response:
  * Success: [STATUS CODE, STRUCTURE]
  * Errors: [POSSIBLE ERROR CODES AND FORMATS]
- Validation: [INPUT VALIDATION RULES]

Include:
- Route handler code
- Input validation logic
- Business logic (or call to service layer)
- Error handling (specific error cases)
- Response formatting
- OpenAPI/Swagger documentation
- Example requests/responses (cURL or code)
- Tests (unit + integration)

Database interaction: [IF APPLICABLE]
External services: [IF ANY]

Create script to process data:

Input data: [FORMAT AND SOURCE]
Output: [DESIRED FORMAT]
Transformations needed: [LIST]
Language: [PYTHON/NODEJS/ETC]

Script requirements:
- Read data from: [FILE/DATABASE/API]
- Transformations:
  [LIST SPECIFIC TRANSFORMATIONS]
- Write output to: [FILE/DATABASE/API]
- Error handling (malformed data, missing values)
- Logging (progress, errors)
- Performance (handle [SIZE]

Create command-line tool for:

Purpose: [WHAT TOOL DOES]
Language: [PREFERRED LANGUAGE]
Main commands: [LIST COMMANDS]

CLI requirements:
- Command structure: [tool] [command] [options]
- Help documentation (--help for each command)
- Version flag (--version)
- Configuration file support
- Output formatting (JSON/table/plain text options)
- Verbose/debug modes
- Color-coded output (for terminal)
- Progress indicators (for long operations)

Commands to implement:
[For each command]
- Command name
- Description
- Arguments (required/optional)
- Options/flags
- Examples

Include:
- Argument parsing (argparse/commander/clap)
- Input validation
- Error messages (helpful, actionable)
- Exit codes (proper status codes)
- Installation instructions
- README with usage examples
- Tests

Package as: [EXECUTABLE/PACKAGE/SCRIPT]

Optimize code performance:

Current code:
[PASTE CODE]

Performance metrics:
- Current execution time: [TIME]
- Target execution time: [TIME]
- Current memory usage: [IF KNOWN]
- Bottlenecks: [IF IDENTIFIED]

Optimization focus:
- [ ] Execution speed
- [ ] Memory usage
- [ ] Network requests
- [ ] Database queries
- [ ] Algorithm efficiency

Profile if needed:
- Identify hotspots (where most time spent)
- Memory allocations
- I/O operations

Provide:
- Optimized code
- Performance improvements (quantified)
- Explanation of optimizations
- Trade-offs (if any)
- Benchmarking code (to verify improvements)
- Recommendations for further optimization

Constraints:
- Must maintain functionality
- [LANGUAGE] version: [VERSION]
- Cannot change: [IF APPLICABLE]

Implement comprehensive error handling for:

Code:
[PASTE CODE]

Perform security audit on:

Code:
[PASTE CODE]

Design database schema for:

Application: [APP PURPOSE]
Database: [PostgreSQL/MySQL/MongoDB/etc]
Data requirements: [WHAT NEEDS TO BE STORED]

Entities needed:
[LIST MAIN ENTITIES/TABLES]

Create regular expression for:

Purpose: [WHAT TO MATCH/VALIDATE]
Language: [JavaScript/Python/etc - for syntax differences]

Requirements:
- Must match: [EXAMPLES OF VALID INPUTS]
- Must not match: [EXAMPLES OF INVALID INPUTS]
- Case sensitivity: [YES/NO]
- Multiline: [YES/NO]

Pattern specifications:
[DETAILED REQUIREMENTS]

Create build configuration for:

Project: [PROJECT NAME]
Build tool: [Webpack/Vite/Rollup/Gradle/Maven/etc]
Environment: [DEVELOPMENT/PRODUCTION/BOTH]

Analyze business strategy for:

Company: [COMPANY NAME]
Industry: [INDUSTRY]
Market position: [LEADER/CHALLENGER/NICHE]
Analysis focus: [SPECIFIC AREA OR COMPREHENSIVE]

Analyze using frameworks:
- SWOT (Strengths, Weaknesses, Opportunities, Threats)
- Porter's Five Forces
- PESTEL (Political, Economic, Social, Technological, Environmental, Legal)
- Value Chain Analysis
- Competitive Positioning

Company information:
- Products/services: [LIST]
- Target market: [DEMOGRAPHICS]
- Revenue model: [HOW THEY MAKE MONEY]
- Key metrics: [IF AVAILABLE]
- Recent developments: [LAST 6-12 MONTHS]

Provide:
- Executive summary (key findings)
- Detailed analysis (each framework)
- Strategic recommendations (prioritized)
- Implementation considerations
- Risk assessment
- Success metrics (how to measure results)

Format: [PRESENTATION/REPORT/MEMO]
Length: [BRIEF/COMPREHENSIVE]
Audience: [WHO'S READING]

Conduct market research on:

Market: [SPECIFIC MARKET/INDUSTRY]
Geography: [REGION/COUNTRY/GLOBAL]
Timeframe: [CURRENT STATE/FORECAST TO YEAR]
Purpose: [MARKET ENTRY/EXPANSION/INVESTMENT DECISION]

Analyze competitors:

Your company: [YOUR COMPANY]
Your product: [YOUR PRODUCT]
Competitors to analyze: [LIST 3-7 COMPETITORS]
Analysis purpose: [POSITIONING/PRICING/FEATURE COMPARISON]

For each competitor:
- Company overview (size, market position, funding)
- Products/services (features, pricing, packages)
- Target market (who they serve)
- Value proposition (how they position themselves)
- Strengths (what they do well)
- Weaknesses (vulnerabilities, gaps)
- Market share (if available)
- Recent moves (launches, pivots, acquisitions)
- Online presence (traffic, social following, reviews)

Comparison matrix:
Features/dimensions: [LIST WHAT TO COMPARE]

Create financial projections for:

Business: [BUSINESS NAME]
Industry: [INDUSTRY]
Stage: [STARTUP/GROWTH/ESTABLISHED]
Projection period: [3 YEARS/5 YEARS]
Purpose: [FUNDRAISING/PLANNING/BUDGETING]

Projection components:
1. Revenue projections
   - Revenue streams breakdown
   - Unit economics (price × volume)
   - Growth assumptions (with justification)
   - Seasonality considerations

2. Expense projections
   - Fixed costs (rent, salaries, etc.)
   - Variable costs (COGS, marketing)
   - Capital expenditures
   - Growth-related expenses

3. Profitability analysis
   - Gross margin
   - Operating margin
   - Net profit margin
   - Break-even analysis

4. Cash flow projections
   - Operating cash flow
   - Investing cash flow
   - Financing cash flow
   - Runway calculation

Key assumptions:
[LIST YOUR ASSUMPTIONS]

Write executive summary for:

Business name: [NAME]
Industry: [INDUSTRY]
Stage: [PRE-LAUNCH/STARTUP/GROWTH]
Target audience: [INVESTORS/PARTNERS/INTERNAL]

Conduct SWOT analysis for:

Company: [COMPANY NAME]
Context: [SPECIFIC INITIATIVE OR OVERALL BUSINESS]
Purpose: [STRATEGIC PLANNING/DECISION-MAKING]

Create customer persona for:

Product/Service: [YOUR OFFERING]
Market: [TARGET MARKET]
Segment: [WHICH CUSTOMER SEGMENT]

Persona components:

1. Demographics
   - Age range
   - Gender
   - Location
   - Income level
   - Education
   - Job title/industry
   - Family status

2. Psychographics
   - Values and beliefs
   - Interests and hobbies
   - Lifestyle
   - Personality traits
   - Attitudes

3. Goals and Motivations
   - What are they trying to achieve?
   - What drives their decisions?
   - What success looks like to them

4. Pain Points and Challenges
   - What problems do they face?
   - What frustrates them?
   - What keeps them up at night?

5. Buying Behavior
   - How do they make decisions?
   - What influences their choices?
   - Budget and price sensitivity
   - Research process
   - Decision timeline

6. Information Sources
   - Where do they learn about products?
   - Trusted sources and influencers
   - Preferred communication channels
   - Social media habits

7. Product Usage
   - How would they use our product?
   - Frequency of use
   - Feature priorities
   - Success metrics for them

Persona format:
- Name and photo description
- Quote (representative statement)
- Background story (narrative)
- One-page profile (all info formatted)

Create: [1/3/5] persona(s)
Use case: [HOW PERSONA WILL BE USED]

Develop go-to-market strategy for:

Product: [PRODUCT NAME]
Company: [COMPANY NAME]
Market: [TARGET MARKET]
Launch timeline: [TIMEFRAME]
Budget: [IF KNOWN]

Create sales pitch deck for:

Company: [COMPANY NAME]
Product: [PRODUCT/SERVICE]
Audience: [WHO YOU'RE PITCHING TO]
Pitch goal: [CLOSE DEAL/DEMO/PARTNERSHIP]
Deck length: [10/15/20 SLIDES]

Slide-by-slide structure:

Slide 1: Title
- Company name and logo
- Tagline
- Contact information

Slide 2: Problem
- Customer pain points (3-5 bullets)
- Current situation and cost of status quo
- Emotional hook

Slide 3: Solution
- Product introduction
- How it solves the problem
- Key benefits (not features yet)

Slide 4: How It Works
- Product demo or workflow
- 3-step process visual
- Ease of use emphasis

Slide 5: Key Features
- 3-4 standout features
- Each with icon/visual + description
- Benefits oriented

Slide 6: Differentiation
- "Why us" over competitors
- Unique advantages
- Proof points

Slide 7: Social Proof
- Customer logos
- Testimonial quotes
- Case study snapshot

Slide 8: Results/ROI
- Customer success metrics
- Quantified outcomes
- Return on investment calculation

Slide 9: Pricing
- Pricing tiers (if applicable)
- Value for each tier
- Flexible payment options

Slide 10: Implementation
- Onboarding process
- Timeline to value
- Support and services

Slide 11: About Us
- Company overview
- Team credentials
- Relevant experience

Slide 12: Call to Action
- Next steps
- Clear ask
- Contact information

For each slide:
- Headline (main point)
- Supporting points (3-5 bullets)
- Visual description (image/chart suggestion)

Tone: [CONSULTATIVE/DIRECT/EDUCATIONAL]
Style: [MINIMALIST/DATA-HEAVY/VISUAL]

Define OKRs for:

Organization level: [COMPANY/DEPARTMENT/TEAM]
Time period: [QUARTER/YEAR]
Strategic priority: [GROWTH/EFFICIENCY/INNOVATION/etc]

OKR framework:

Objective 1: [QUALITATIVE GOAL]
Description: [WHAT YOU WANT TO ACHIEVE AND WHY]

Key Result 1.1: [MEASURABLE OUTCOME]
- Baseline: [CURRENT STATE]
- Target: [DESIRED STATE]
- Measurement method: [HOW TO TRACK]

Key Result 1.2: [MEASURABLE OUTCOME]
- Baseline: [CURRENT STATE]
- Target: [DESIRED STATE]
- Measurement method: [HOW TO TRACK]

Key Result 1.3: [MEASURABLE OUTCOME]
- Baseline: [CURRENT STATE]
- Target: [DESIRED STATE]
- Measurement method: [HOW TO TRACK]

[REPEAT FOR OBJECTIVE 2, 3, etc]

Create: [3-5] Objectives
Each with: [2-4]

Create meeting agenda for:

Meeting type: [TEAM MEETING/CLIENT MEETING/BRAINSTORM/DECISION]
Duration: [30/60/90 MINUTES]
Attendees: [WHO WILL BE THERE]
Meeting goal: [WHAT NEEDS TO BE ACCOMPLISHED]

Agenda structure:

Header:
- Meeting title
- Date and time
- Location/Zoom link
- Attendees list
- Meeting leader/facilitator

Pre-meeting preparation:
- Materials to review beforehand
- Pre-reads (attach or link)
- Preparation expected from attendees

Agenda items:
For each item include:
- Topic/discussion point
- Time allocated (be specific)
- Owner/presenter
- Objective (inform/decide/brainstorm/plan)
- Expected outcome

Example format:
1. [TIME] - [TOPIC NAME]
   - Owner: [NAME]
   - Objective: [INFORM/DECIDE]
   - Expected outcome: [WHAT WE NEED]

Parking lot:
- Topics deferred
- Items for next meeting
- Follow-up needed

Closing:
- Next steps and action items (during meeting, fill these in)
- Next meeting date (if recurring)

Meeting guidelines:
- Start/end times firm
- Phones away/laptop closed (if appropriate)
- Decision-making process (if applicable)

Send agenda: [24 HOURS BEFORE MEETING]

Design KPI dashboard for:

Department: [SALES/MARKETING/OPERATIONS/PRODUCT]
User: [EXECUTIVE/MANAGER/INDIVIDUAL CONTRIBUTOR]
Update frequency: [REAL-TIME/DAILY/WEEKLY/MONTHLY]
Purpose: [MONITORING/DECISION-MAKING/REPORTING]

Dashboard sections:

1. Overview/Summary (Top KPIs)
   - 3-5 headline metrics
   - Current value
   - vs target (progress bar or %)
   - Trend indicator (up/down/flat)

2. Performance Deep Dive
   Primary metrics:
   - [METRIC NAME]: [CURRENT]/[TARGET]
   - Visualization: [CHART TYPE]
   - Time period: [THIS WEEK/MONTH/QUARTER]
   - Comparison: [VS LAST PERIOD/VS GOAL]

3. Breakdown/Segmentation
   - By channel/product/region/team
   - Table or bar chart
   - Sortable by key dimension

4. Trends Over Time
   - Line charts showing history
   - Multiple metrics comparable
   - Annotations for significant events

5. Alerts/Attention Items
   - Metrics below threshold (red flags)
   - Metrics exceeding expectations (wins)
   - Action items generated from data

For each KPI:
- Metric name (clear, business-friendly)
- Definition (how it's calculated)
- Why it matters (business relevance)
- Target/benchmark
- Data source
- Update frequency
- Who owns this metric

Visual hierarchy:
- Most important metrics largest/top
- Use color coding (green/yellow/red)
- Whitespace for readability

Interactivity:
- Filters (date range, segment, etc.)
- Drill-down capability
- Export options

Dashboard layout: [DESCRIBE STRUCTURE]
Tools: [TOOL IF KNOWN - Tableau, PowerBI, custom]

Create project charter for:

Project name: [PROJECT NAME]
Project sponsor: [EXECUTIVE SPONSOR]
Project manager: [NAME]
Start date: [DATE]
Target completion: [DATE]

Project charter sections:

1. Executive Summary
   - Project overview (2-3 paragraphs)
   - Business need/opportunity
   - Expected outcomes

2. Project Objectives
   - SMART objectives (Specific, Measurable, Achievable, Relevant, Time-bound)
   - Success criteria
   - How success will be measured

3. Scope
   In scope:
   - [LIST WHAT'S INCLUDED]
   
   Out of scope:
   - [LIST WHAT'S EXPLICITLY EXCLUDED]
   
   Assumptions:
   - [LIST ASSUMPTIONS]
   
   Constraints:
   - [BUDGET/TIME/RESOURCE CONSTRAINTS]

Develop change management plan for:

Change: [WHAT'S CHANGING]
Organization: [COMPANY/DEPARTMENT]
Impacted population: [WHO'S AFFECTED]
Change magnitude: [MINOR/MODERATE/MAJOR]
Timeline: [IMPLEMENTATION TIMEFRAME]

Change management components:

1. Change Overview
   - What's changing and why
   - Current state vs future state
   - Business case for change

2. Stakeholder Analysis
   - Who's impacted (list groups)
   - Impact level (high/medium/low per group)
   - Resistance factors
   - Influence and buy-in strategy

3. Communication Plan
   - Key messages (what to communicate)
   - Communication channels (how)
   - Frequency and timing (when)
   - Audience segmentation (who gets what)
   - Feedback mechanisms

4. Training Plan
   - Training needs assessment
   - Training delivery methods
   - Training schedule
   - Materials and resources
   - Success metrics (post-training evaluation)

5. Resistance Management
   - Anticipated resistance points
   - Root causes
   - Mitigation strategies
   - Escalation process

6. Support Structure
   - Change champions (identify and train)
   - Help desk or support resources
   - FAQ and documentation
   - Office hours or Q&A sessions

7. Implementation Roadmap
   - Phase 1, 2, 3... (what happens when)
   - Quick wins (early successes to build momentum)
   - Milestones
   - Go/no-go decision points

8. Measurement and Monitoring
   - Adoption metrics (usage, engagement)
   - Resistance indicators
   - Success criteria
   - Feedback loops

9. Reinforcement and Sustainment
   - Post-launch support
   - Continuous improvement process
   - Celebrating successes
   - Lessons learned capture

Deliverables:
- Change management plan document
- Communication templates
- Training materials outline
- Stakeholder map
- Timeline/Gantt chart

Approach: [KOTTER/ADKAR/LEAN CHANGE MANAGEMENT]

Prepare quarterly business review for:

Company: [COMPANY NAME]
Quarter: [Q1/Q2/Q3/Q4] [YEAR]
Audience: [BOARD/INVESTORS/LEADERSHIP TEAM]
Presentation format: [SLIDES/REPORT/MEETING]

QBR structure:

1. Executive Summary
   - Quarter highlights (top 3-5 achievements)
   - Challenges faced
   - Financial summary
   - Outlook for next quarter

2. Financial Performance
   - Revenue (actual vs plan)
   - Expenses (vs budget)
   - Profitability metrics
   - Cash flow and runway
   - Key financial ratios
   
   Present: Tables, charts showing trends

3. Operational Metrics
   - Department-specific KPIs
   - vs previous quarter
   - vs same quarter last year
   - vs annual targets
   
   For each metric: Status (on track/at risk/off track)

4. Customer Metrics
   - New customers acquired
   - Churn/retention rate
   - Customer satisfaction (NPS, CSAT)
   - Lifetime value trends
   - Support metrics

5. Product/Service Updates
   - New features/products launched
   - Product performance
   - Roadmap progress
   - User feedback themes

6. Sales and Marketing
   - Pipeline health
   - Lead generation
   - Conversion rates
   - Campaign performance
   - Win/loss analysis

7. People and Culture
   - Headcount changes
   - Key hires
   - Turnover rate
   - Employee satisfaction
   - DEI metrics (if tracked)

8. Strategic Initiatives
   - Progress on OKRs
   - Major projects status
   - Milestones achieved
   - Blockers and challenges

9. Competitive Landscape
   - Market changes
   - Competitor moves
   - Our relative position

10. Risks and Mitigation
   - Top risks identified
   - Impact and probability
   - Mitigation plans
   - New risks emerged

11. Priorities for Next Quarter
   - Top 3-5 priorities
   - Resource allocation
   - Success criteria
   - Dependencies

12. Questions and Discussion
   - Open topics for board input
   - Decisions needed
   - Support requested

Formatting:
- Data visualizations (charts, graphs)
- Traffic light system (green/yellow/red)
- Commentary alongside data (context matters)
- Appendix with detailed data

Tone: Honest, balanced (celebrate wins, acknowledge challenges)
Length: [30/60/90 MINUTE PRESENTATION]

Write RFP response for:

RFP from: [CLIENT NAME]
Your company: [YOUR COMPANY]
Service/product: [WHAT THEY'RE REQUESTING]
Submission deadline: [DATE]
RFP requirements: [KEY REQUIREMENTS]

Create email newsletter strategy for:

Business: [BUSINESS NAME]
Industry: [INDUSTRY]
Target audience: [SUBSCRIBER DEMOGRAPHIC]
Current list size: [NUMBER OR STARTING FROM 0]
Goals: [ENGAGEMENT/SALES/BRAND AWARENESS]

Develop crisis communication plan for:

Organization: [ORGANIZATION NAME]
Industry: [INDUSTRY]
Potential crisis scenarios: [LIST IF KNOWN]

Crisis communication plan elements:

1. Crisis Definition
   - What constitutes a crisis for your organization
   - Severity levels (Tier 1/2/3)
   - Triggers for plan activation

2. Crisis Management Team
   - Team members (roles and responsibilities)
     * Crisis Lead
     * Communications Lead
     * Legal Counsel
     * Subject Matter Experts
   - Decision-making authority
   - Contact information (24/7)
   - Backup personnel

3. Response Procedures
   Step-by-step:
   - Crisis identified
   - Team notification (within X hours)
   - Situation assessment
   - Initial response (holding statement)
   - Ongoing communication
   - Resolution and follow-up

4. Communication Protocols
   Internal:
   - Employee notification process
   - Information cascade
   - Internal updates frequency
   
   External:
   - Media relations process
   - Customer communication
   - Partner/vendor notifications
   - Social media protocols
   - Website updates

5. Message Development
   - Holding statements (template)
   - Key messages framework
   - Q&A preparation
   - Spokesperson guidelines
   - Tone and language guidance

6. Stakeholder Matrix
   - Priority stakeholders (list and prioritize)
   - Communication method per stakeholder
   - Timing requirements
   - Information needs

7. Channel Strategy
   - Primary channels (press release, social, email)
   - Monitoring channels (social listening, media monitoring)
   - Dark site or crisis page (when to activate)
   - Call center scripts

8. Monitoring and Intelligence
   - Social media monitoring tools
   - Media monitoring process
   - Sentiment tracking
   - Rumor control process

9. Documentation
   - Incident log template
   - All communications archived
   - Decision rationale captured
   - Timeline tracking

10. Post-Crisis Activities
   - Debrief process
   - Lessons learned documentation
   - Plan updates
   - Reputation repair strategy
   - Thank you communications

Scenarios and Response:
[For 3-5 potential scenarios]

Create comprehensive product launch checklist for:

Product: [PRODUCT NAME]
Launch date: [TARGET DATE]
Product type: [NEW PRODUCT/NEW FEATURE/MAJOR UPDATE]
Target market: [AUDIENCE]

Launch checklist categories:

PRE-LAUNCH (12-8 weeks before)
Product Development:
- [ ] Feature complete and tested
- [ ] Beta testing completed
- [ ] Product documentation finalized
- [ ] Training materials created
- [ ] Support resources prepared

Positioning and Messaging:
- [ ] Value proposition defined
- [ ] Positioning vs competitors documented
- [ ] Key messages developed
- [ ] Customer pain points and solutions mapped
- [ ] Elevator pitch finalized

Go-to-Market Strategy:
- [ ] Target market segments identified
- [ ] Pricing strategy confirmed
- [ ] Distribution channels selected
- [ ] Sales strategy defined
- [ ] Marketing plan approved

PRE-LAUNCH (8-4 weeks before)
Marketing Assets:
- [ ] Website/landing page created
- [ ] Product videos produced
- [ ] Case studies/testimonials gathered
- [ ] Sales collateral designed
- [ ] Demo environment set up

Team Preparation:
- [ ] Sales team trained
- [ ] Customer support trained
- [ ] FAQs documented
- [ ] Internal launch communicated
- [ ] Partner enablement completed

Marketing Campaign:
- [ ] PR strategy developed
- [ ] Media outreach initiated
- [ ] Social media calendar created
- [ ] Email campaigns drafted
- [ ] Paid advertising campaigns set up

PRE-LAUNCH (4-0 weeks before)
Final Preparations:
- [ ] Launch day timeline created
- [ ] Crisis management plan ready
- [ ] Monitoring tools configured
- [ ] Success metrics defined
- [ ] Launch team roles confirmed

Soft Launch/Testing:
- [ ] Soft launch to select customers (if applicable)
- [ ] Feedback gathered and addressed
- [ ] Final bug fixes deployed
- [ ] Performance/scale testing completed

Communications:
- [ ] Press release finalized
- [ ] Launch email ready
- [ ] Social posts scheduled
- [ ] Influencer outreach completed
- [ ] Internal announcements prepared

LAUNCH DAY
- [ ] Product goes live
- [ ] Press release distributed
- [ ] Email announcement sent
- [ ] Social media announcements posted
- [ ] Sales team activated
- [ ] Customer support standing by
- [ ] Website analytics monitoring
- [ ] Social listening active
- [ ] Media monitoring in place

POST-LAUNCH (1-4 weeks after)
Week 1:
- [ ] Monitor metrics (signups, trials, sales)
- [ ] Respond to customer feedback
- [ ] Media coverage tracked
- [ ] Social sentiment analyzed
- [ ] Support issues addressed
- [ ] Quick wins identified and promoted

Week 2-4:
- [ ] Campaign performance reviewed
- [ ] A/B tests evaluated
- [ ] Customer interviews conducted
- [ ] Sales feedback gathered
- [ ] Product adjustments prioritized
- [ ] Post-launch report created

Ongoing:
- [ ] Regular metrics review
- [ ] Continuous improvement cycle
- [ ] Customer success tracking
- [ ] Competitive response monitoring

For each item:
- Owner (who's responsible)
- Due date (when it must be done)
- Status (not started/in progress/complete)
- Dependencies (what else must be done first)

Launch Success Criteria:
[DEFINE WHAT SUCCESS LOOKS LIKE]
- [METRIC]: [TARGET]
- [METRIC]: [TARGET]

Design annual report structure for:

Organization: [ORGANIZATION NAME]
Fiscal year: [YEAR]
Report audience: [SHAREHOLDERS/STAKEHOLDERS/PUBLIC]
Report length: [20/40/60 PAGES]
Tone: [FORMAL/ACCESSIBLE/INSPIRATIONAL]

Annual report sections:

FRONT MATTER
- Cover (compelling visual, organization name, fiscal year)
- Table of Contents
- Letter to Shareholders (2-3 pages)
  * Year in review (highlights)
  * Strategic progress
  * Financial summary
  * Outlook and vision
  * Personal note from CEO

STRATEGIC OVERVIEW
- Mission, Vision, Values (if changed or worth restating)
- Year in Review
  * Timeline of major milestones
  * Key achievements by quarter
  * Awards and recognition
- Strategic Priorities
  * Current priorities explained
  * Progress on each
  * Alignment with mission

BUSINESS PERFORMANCE
- Business Model Overview (how the organization creates value)
- Market Position
  * Industry context
  * Competitive landscape
  * Market trends
- Operational Highlights by Division/Product Line
  * Performance metrics
  * Growth initiatives
  * Challenges and responses

FINANCIAL PERFORMANCE
- Financial Highlights (infographic-style summary)
- Revenue Analysis
  * Revenue breakdown (by segment, geography, product)
  * Year-over-year comparison
  * Growth drivers
- Profitability
  * Margins and trends
  * Cost management initiatives
- Balance Sheet Strength
  * Assets, liabilities, equity
  * Cash position
  * Debt levels
- Cash Flow
  * Operating, investing, financing activities
  * Capital allocation priorities
- Financial Statements
  * Income statement
  * Balance sheet
  * Cash flow statement
  * Notes to financial statements

IMPACT AND SUSTAINABILITY
- Environmental Impact
  * Carbon footprint
  * Sustainability initiatives
  * Progress on environmental goals
- Social Responsibility
  * Community involvement
  * Diversity and inclusion metrics
  * Employee wellbeing programs
- Governance
  * Board composition
  * Ethics and compliance
  * Risk management

PEOPLE AND CULTURE
- Employee Metrics
  * Headcount and growth
  * Retention and satisfaction
  * Training and development
- Leadership Team
  * Executive bios
  * Board of Directors
- Culture Initiatives
  * Values in action (stories/examples)
  * Employee testimonials

LOOKING AHEAD
- Industry Outlook
  * Trends shaping the market
  * Opportunities and challenges
- Strategic Roadmap
  * Priorities for coming year
  * Investments planned
  * Expected outcomes
- Risk Factors
  * Key risks identified
  * Mitigation strategies

BACK MATTER
- Corporate Information
  * Company details (headquarters, locations)
  * Contact information
  * Stock information (if public)
  * Transfer agent
- Appendices
  * Detailed financial data
  * Technical information
  * Glossary (if needed)

Design Guidelines:
- Visual hierarchy (clear sections, scannable)
- Data visualization (charts, infographics)
- Photography (people, products, operations)
- Consistent branding (colors, fonts, style)
- Accessible (readable fonts, clear language)

Distribution:
- Print copies (for whom)
- Digital PDF (website, email)
- Investor relations portal
- Regulatory filings (if required)

Compliance:
- Accounting standards (GAAP, IFRS)
- Regulatory requirements (SEC, etc.)
- Legal review and approval
- Auditor sign-off

Timeline for creation: [MONTHS REQUIRED]
Budget: [IF APPLICABLE]