Meeting & Collaboration Prompts

I want you to act as a virtual event planner, responsible for organizing and executing online conferences, workshops, and meetings. Your task is to design a virtual event for a tech company, including the theme, agenda, speaker lineup, and interactive activities. The event should be engaging, informative, and provide valuable networking opportunities for attendees. Please provide a detailed plan, including the event concept, technical requirements, and marketing strategy. Ensure that the event is accessible and enjoyable for a global audience.

Based on my prior interactions with person, give me 5 things likely top of mind for our next meeting.

Summarize the meeting transcript by performing the following tasks:

- **State the Meeting Objective**: Begin with a brief paragraph (2-3 sentences) explaining the overall objective or purpose of the meeting based on the content provided.
- **Meeting Summary**: Write a concise summary paragraph (5-8 sentences) capturing the main topics discussed and general outcome.
- **Meeting Title**: Create a clear and descriptive title for the meeting.
- **Discussion Points**: List the key discussion points addressed during the meeting in bullet points.
- **Decisions Made**: Summarize all concrete decisions, resolutions, or agreements reached.
- **Action Items**: List all action items, each assigned to a specific individual, including due dates if mentioned.

Ensure that your output follows this order:  
1. Meeting Title  
2. Meeting Objective  
3. Meeting Summary  
4. Key Discussion Points  
5. Decisions Made  
6. Action Items & Responsibilities

**Reasoning Order**:  
- First, identify the objective and content of the meeting, reason through the important points, summarize, and then state any conclusions such as assigned tasks, decisions, etc.  
- Do not start with conclusions or lists—always present the reasoning/summary before results or actionables.

**Output Format**:  
Use markdown formatting, with clearly labeled sections and bullet lists where appropriate. Output should be ~2-3 paragraphs for objectives and summary, with bullet lists for points, decisions, and action items.

**Example Output** (fill in with actual meeting details as appropriate):

Meeting Title: [Descriptive Title of Meeting]

**Meeting Objective:**  
The objective of this meeting was to review the status of the upcoming product launch and address any outstanding challenges. Participants discussed current progress, identified roadblocks, and set clear next steps to ensure timely delivery.

**Meeting Summary:**  
During the meeting, team members shared updates on marketing, engineering, and logistics. Several potential delays were identified, and alternative solutions were brainstormed. The group agreed on prioritizing bug fixes and accelerating outreach efforts. Key deadlines were reaffirmed, and new responsibilities were assigned to address gaps in readiness.

**Key Discussion Points:**
- Progress updates from each department
- Major blockers and proposed solutions
- Resource needs and reallocations
- Communication plan moving forward

**Decisions Made:**
- Proceed with expedited bug-fix schedule
- Shift two resources from support to engineering until launch
- Approve new marketing materials

**Action Items & Responsibilities:**
- [Alice] Finalize bug list by Friday
- [Ben] Update marketing assets by next Wednesday
- [Chloe] Coordinate logistics with new suppliers by end of week

**Important:**  
- Always begin with objective and summary before listing points, decisions, or action items.
- Be concise, clear, and accurate in capturing meeting highlights.

---

**Reminder:**  
- Always capture the meeting objective and provide a summary first, then enumerate key points, decisions, and responsibilities.  
- Assign all action items explicitly to individuals.  
- Begin output with a meeting title.

Summarize and export all important points, instructions, and contextual information exchanged in this chat, structured per your requirements.

- Use section headers for each major category (e.g., Task Instructions, Preferences, System Guidelines, etc.).
- For each entry within a category, list one entry per line, formatted as: [YYYY-MM-DD] - Entry content here.
- Sort entries by oldest date first within each category.
- If no date is known for an entry, use [unknown] instead of a date.
- When preserving user content, use the original wording verbatim where possible, particularly for direct instructions, requirements, or preferences.
- Wrap the entire export in a single code block (backticks, language unspecified) for easy copying.
- After the code block, clearly state whether this is the complete set or if more entries remain.

Persist in checking all prior conversation turns to ensure all relevant context is captured exhaustively. Think step-by-step to avoid missing any category or detail.

## Output Format:
- The export must be wrapped in a single code block.
- Use markdown section headers within the code block for each category.
- Each entry in a category must be a single line, formatted as: [YYYY-MM-DD] - Entry content here.
- If needed, use [unknown] if the date for an entry cannot be determined.
- After the code block, add a plain text statement: "This is the complete set." or "More entries remain." (as appropriate).

## Example

```
# Task Instructions
[2024-06-13] - I will move this chant to another AI agent to also support my projects. I want you to prepare detailed list of important points which were discussed in this chat. Please preapare.

# Format Specifications
[2024-06-13] - Use section headers for each category. Within each category, list one entry per line, sorted by oldest date first. Format each line as: [YYYY-MM-DD] - Entry content here.
[2024-06-13] - If no date is known, use [unknown] instead.

# Output Instructions
[2024-06-13] - Wrap the entire export in a single code block for easy copying.
[2024-06-13] - After the code block, state whether this is the complete set or if more remain.
```

(Real exports may be longer and contain more categories/entries as appropriate.)

---

**Reminder:** Carefully review all prior turns to ensure nothing is missed, using verbatim wording for user requirements and instructions. Produce the export exactly as described above, including the final completeness statement.

### System Role & Objective
You are a senior video game industry equity analyst. Your objective is to conduct a forensic financial and sales trajectory analysis for games.

### Required Analysis Framework

#### 1. Baseline Market Performance & Context
*   **Retail Metrics:** Detail the baseline sales performance across Steam, PS5, and Xbox platforms, highlighting total unit sales versus generated revenue.
*   **The "Niche" Penalty:** Quantify the market constraints of the genre

#### 2. Subscription-Model Distortion (The Game Pass Factor)
*   **Cannibalization vs. De-risking:** Model the financial trade-off of accepting a guaranteed, upfront, partner-publishing licensing fee from Microsoft versus the immediate flatlining of standard retail discovery on PC and Xbox storefronts.
*   **Player Migration:** Analyze the disparity between stagnant premium unit sales and healthy concurrent user (CCU) engagement metrics via subscription ecosystems.

#### 3. Macro Pricing & Discount Trajectory Model
*   **Publisher Behavioral Baseline:** Compare the game's post-launch pricing to historical publisher patterns 
*   **Accelerated Markdown Modeling:** Map out the specific chronological timeline where the publisher was forced to abandon its traditional playbook due to flatlined retail discovery, tracking the progression from strict launch pricing to deep promotional discounts (e.g., ~40% off within six months).

#### 4. Micro-Metric Sales Trajectory 
*   **The Post-Holiday Hangover:** Model the exact unit sales velocity during a standard post-launch window.
*   **Content-Driven Resurgence:** Analyze how targeted post-launch DLC acts as a secondary marketing vehicle, measuring the month-over-month percentage spikes in base-game retail acquisition driven by community-sentiment course corrections.

### Output Deliverable Requirements
*   **Data Structures:** Present comparative metrics (Historical vs. Current, Month-over-Month trajectory) using clean Markdown tables.
*   **Visual Timelines:** Include text-based ASCII or structural mapping diagrams to clearly illustrate the discount and sales-stagnation inflection points over a 24-month lifecycle, factoring spring, summer, autumn, and winter steam sales patterns
*   **Tone:** Highly analytical, objective, and dense with industry-standard financial and gaming metrics (e.g., CCU, front-loading factors, licensing offsets, long-tail revenue).

Act as a project manager. you are to create proposal of a team for an event using data from existing documents uploaded and made in Notion. 

Your task is to:
- Analyze existing project documents stored in Notion to gather relevant data.
- Collaborate with team members to identify key points and objectives for the proposal.
- Draft a detailed proposal highlighting the team's goals, strategies, and expected outcomes for the conference.

Rules:
- Ensure the proposal is clear, concise, and aligns with the overall objectives of the conferenceproposal.
- Include input from all relevant stakeholders in the proposal.

make a flyer for a  leadership summit using the other flyer with the lady as a reference  for the format, it should replace the picture of the lady with that of the male figure, make use of the logo that has the sun and eagle . the name of the ministry is CYPRUS REVIVAL HUB, 



the boy or copy is: LEADERSHIP SUMMIT with Ejim Vincent Chidera(Set Man), please not the set man should be underneath

The three pillars in this order is, Fellowship,Discipleship,Leadership,



date is 25&26 September 2026, 

venue is google meet(use logo of google meet)



Time : 10:30pm cyprus time and 8:30pm Nigerian time,