angen.ai
← Back to Documentation
Advanced Features•7 min read

Meetings

Store meeting transcripts and notes to provide context for AI code generation - transform discussions into requirements and code.

Meetings

Meetings in AngenAI store meeting transcripts and notes that you can attach to Work Items as context. This guide covers creating, managing, and using meeting content to inform AI code generation.

What Are Meetings?

Meetings are text blocks containing notes, transcripts, or summaries from your team discussions. When attached to a Work Item, AI uses meeting content to understand:
  • Requirements discussed in planning sessions
  • Technical decisions from architecture meetings
  • Feature specifications from stakeholder calls
  • Bug reports from triage meetings
Meeting context helps AI generate code that aligns with your team's decisions and discussions.

Accessing Meetings

Click Meetings in the sidebar to open the Meetings editor.
The editor has the same layout as Knowledge and Personalities:
  • Left panel: List of meeting entries organized by scope
  • Right panel: Markdown editor for meeting content

Creating Meeting Entries

Create a New Meeting

  1. Click Create next to the Organization or Project section header
  2. Enter a name (e.g., "Sprint Planning - Jan 15" or "Auth Feature Discussion")
  3. Add your meeting content in the editor
  4. Click Save

Import from Markdown Files

  1. Drag a .md file containing meeting notes into the editor
  2. AngenAI creates a meeting entry with the filename
  3. Edit the name and content as needed
  4. Save the entry

Meeting Content Structure

Structure your meeting content for AI comprehension:

Basic Structure

# Sprint Planning - January 15, 2025

## Attendees
- Alice (Product Owner)
- Bob (Tech Lead)
- Carol (Developer)

## Topics Discussed

### User Authentication Feature
- Decision: Use JWT tokens with 24-hour expiration
- Refresh tokens stored in HTTP-only cookies
- Social login (Google, GitHub) planned for Phase 2

### Dashboard Redesign
- New layout approved by design team
- Charts library: Recharts selected
- Mobile-first approach required

## Action Items
- [ ] Bob: Create auth service architecture doc
- [ ] Carol: Implement JWT middleware
- [ ] Alice: Finalize dashboard requirements

For Technical Decisions

# Architecture Decision: Database Selection

## Date
January 10, 2025

## Context
Need to choose database for new microservice handling user analytics.

## Options Considered
1. PostgreSQL - Familiar, strong consistency
2. MongoDB - Flexible schema, horizontal scaling
3. TimescaleDB - Time-series optimized

## Decision
TimescaleDB selected for:
- Native time-series support
- PostgreSQL compatibility
- Automatic data retention policies

## Consequences
- Team needs TimescaleDB training
- Existing PostgreSQL tools still work
- Migration path available if needed

For Bug Triage

# Bug Triage - January 12, 2025

## Critical Issues

### BUG-1234: Login fails on mobile Safari
- Priority: P0
- Assigned: Carol
- Root cause: Cookie SameSite attribute
- Fix: Set SameSite=None; Secure

### BUG-1235: Dashboard slow on large datasets
- Priority: P1
- Assigned: Bob
- Cause: N+1 query in chart data fetch
- Fix: Batch queries, add pagination

## Deferred Issues
- BUG-1200: Minor UI alignment (P3)
- BUG-1198: Tooltip positioning edge case (P3)

Meeting Scopes

Organization-Wide Meetings

Available across all projects. Use for:
  • Company-wide architecture decisions
  • Cross-team planning sessions
  • Organization standards discussions
Only Admins and Owners can create organization-wide meetings.

Project-Scoped Meetings

Available only within a specific project. Use for:
  • Sprint planning notes
  • Feature discussions
  • Project-specific technical decisions
All members can create project-scoped meetings.

Using Meetings in Work Items

From the Context Panel

  1. Open a Work Item
  2. Expand the Meetings section in the Context Panel
  3. Check the meetings relevant to your task
  4. Submit your prompt
AI reads the meeting content when generating output.

Example: Generating Code from Meeting Notes

Meeting content:
# Feature Discussion: User Profile

## Requirements
- Display user avatar, name, and email
- Edit button opens modal form
- Save changes with optimistic update
- Show loading state during save
Work Item prompt:
Implement the user profile component based on the requirements
from our feature discussion meeting.
AI generates code following the specifications from the meeting notes.

Example: Generating Requirements Documentation

Transform raw meeting transcripts into structured requirements:
  1. Add your meeting transcript to the Meetings section
  2. Create a new Work Item
  3. Attach the meeting in the Context Panel
  4. Select a "Requirements Analyst" or "Project Manager" Personality
  5. Prompt: 
    Analyze the attached meeting transcript and generate structured
requirements documentation. Include user stories, acceptance
criteria, and technical constraints.
  6. AI generates Knowledge articles with organized requirements
  7. Review the output and save to your Knowledge Base
This workflow transforms informal meeting discussions into formal documentation that developers can reference when generating code.

Managing Meetings

Editing Meetings

  1. Select the meeting from the list
  2. Update the content in the editor
  3. Click Save

Renaming Meetings

Use clear, searchable names:
  • Include date: "Sprint Planning - Jan 15"
  • Include topic: "Auth Feature Discussion"
  • Include project: "Mobile App - Kickoff Meeting"

Duplicating Meetings

  1. Select the meeting
  2. Click Duplicate
  3. Edit for a new meeting (e.g., recurring meeting template)
  4. Save with updated name and content

Moving Between Scopes

  1. Select the meeting
  2. Click Move
  3. Choose Organization or Project scope
Note: Members cannot move meetings to organization scope.

Deleting Meetings

  1. Select the meeting
  2. Click Delete
  3. Confirm deletion

Best Practices

Keep Meetings Focused

Create separate entries for different topics:
  • One entry per meeting or discussion
  • Split long meetings by topic if needed
  • Use clear naming conventions

Update After Meetings

Add meeting notes promptly while details are fresh:
  1. Create the entry during or after the meeting
  2. Include key decisions and action items
  3. Note any open questions

Reference Decisions

When decisions affect code:
## Decision: API Response Format

All API endpoints must return:
\`\`\`json
{
  "success": boolean,
  "data": object | null,
  "error": string | null,
  "timestamp": string
}
\`\`\`
This gives AI specific patterns to follow.

Link to Related Content

Reference other documentation:
## Related
- See Knowledge Base: "API Documentation"
- Architecture diagram in Media Library
- Previous meeting: "API Design Discussion - Dec 20"

Use Cases

Sprint Planning

Store sprint goals and user stories:
# Sprint 23 Planning

## Goals
1. Complete user authentication flow
2. Implement dashboard charts
3. Fix critical mobile bugs

## User Stories
- As a user, I can log in with email/password
- As a user, I can see my activity chart
- As a mobile user, I can use the app on Safari

Technical Decisions

Document architecture and technology choices:
# Tech Decision: State Management

## Decision
Use Zustand for state management instead of Redux.

## Rationale
- Simpler API, less boilerplate
- Better TypeScript support
- Smaller bundle size
- Team familiarity

Feature Specifications

Capture detailed requirements:
# Feature Spec: Notification System

## Requirements
- Real-time notifications via WebSocket
- Notification bell with unread count
- Dropdown showing last 10 notifications
- Mark as read on click
- "Mark all as read" button

Retrospectives

Store lessons learned:
# Sprint 22 Retrospective

## What Worked
- Pair programming on complex features
- Daily standups at 9:30 AM

## What Didn't Work
- Too many meetings on Wednesdays
- PR reviews taking too long

## Action Items
- Limit Wednesday meetings to 2 hours
- Set 24-hour PR review SLA

Troubleshooting

AI Misses Meeting Context

  • Check that the meeting is selected in the Context Panel
  • Ensure relevant sections are clearly formatted
  • Add more specific details to the meeting content

Cannot Find Meeting

  • Check the current project scope
  • Use search to filter by name
  • Verify the meeting wasn't deleted

Meeting Too Long

For lengthy meetings:
  • Create summary sections at the top
  • Split into multiple entries by topic
  • Highlight key decisions prominently

What's Next?