CODITECT Standard: Meeting Analysis

Document: CODITECT-STANDARD-MEETING-ANALYSIS
Version: 1.0.0
Purpose: Define standards for meeting analysis, decision extraction, and action tracking
Audience: CODITECT users processing meeting notes and transcripts
Date Created: 2026-01-13
Status: ACTIVE
Related Documents:
  - coditect-core-standards/TEMPLATES/MEETING-ANALYSIS-TEMPLATE.md
  - agents/meeting-notes-analyzer.md
  - skills/meeting-analysis-patterns/SKILL.md
  - commands/analyze-meeting.md

Purpose

This standard defines how to analyze meeting notes, transcripts, and recordings to:

Extract key decisions and their rationale
Identify action items with owners and deadlines
Capture strategic intent and business context
Preserve institutional knowledge in searchable format
Enable pattern detection across meeting history

Meeting Analysis Framework

1. Document Classification

Every meeting analysis must identify the meeting type:

Type	Description	Key Focus Areas
`strategic`	Board, executive, planning meetings	Decisions, priorities, resource allocation
`operational`	Standups, check-ins, status updates	Blockers, progress, coordination
`technical`	Architecture, design, code reviews	Technical decisions, trade-offs, patterns
`sales`	Customer calls, demos, negotiations	Requirements, objections, commitments
`advisory`	Mentor, advisor, consultant sessions	Recommendations, guidance, connections
`legal`	Contract reviews, compliance, governance	Terms, risks, obligations

2. Required Extraction Elements

Every meeting analysis MUST extract:

metadata:
  date: "YYYY-MM-DD"
  time: "HH:MM TZ"
  duration: "XX minutes"
  type: strategic|operational|technical|sales|advisory|legal
  participants:
    - name: "Full Name"
      role: "Role/Title"
      organization: "Company/Team"
  location: "Virtual/Physical location"
  recording_source: "Gemini|Otter|Manual|etc."

decisions:
  - id: "D-YYYYMMDD-001"
    decision: "Clear statement of what was decided"
    rationale: "Why this decision was made"
    alternatives_considered:
      - option: "Alternative A"
        rejected_reason: "Why rejected"
    participants_involved: ["Name1", "Name2"]
    confidence: high|medium|low
    reversibility: easy|moderate|difficult|irreversible

action_items:
  - id: "AI-YYYYMMDD-001"
    action: "Specific action to be taken"
    owner: "Name"
    deadline: "YYYY-MM-DD or 'within X days'"
    priority: critical|high|medium|low
    dependencies: ["AI-YYYYMMDD-002"]
    status: pending|in_progress|completed|blocked

key_topics:
  - topic: "Topic name"
    summary: "2-3 sentence summary"
    sentiment: positive|neutral|negative|mixed
    strategic_importance: high|medium|low

agreements:
  - parties: ["Party A", "Party B"]
    terms: "What was agreed"
    conditions: "Any conditions or contingencies"
    documentation_required: true|false

concerns_raised:
  - concern: "Description of concern"
    raised_by: "Name"
    resolution: "How it was addressed or 'unresolved'"
    follow_up_required: true|false

3. Analysis Quality Criteria

Grade	Score	Criteria
A	90-100%	All decisions captured with rationale, all action items have owners/deadlines, strategic context clear
B	80-89%	Most decisions captured, action items assigned, minor gaps in rationale
C	70-79%	Key decisions present but rationale incomplete, some action items missing owners
D	60-69%	Significant gaps in decision capture, action items unclear
F	<60%	Missing critical decisions, no clear action items

Decision Documentation Standard

Decision Severity Classification

CRITICAL: Affects company direction, funding, partnerships, legal standing
HIGH: Affects multiple teams, significant resources, customer commitments
MEDIUM: Affects single team/product area, moderate resources
LOW: Operational details, minor process changes

Decision Documentation Format

## Decision: [D-YYYYMMDD-XXX] {Title}

**Status:** DECIDED | PENDING | DEFERRED
**Severity:** CRITICAL | HIGH | MEDIUM | LOW
**Date:** YYYY-MM-DD
**Participants:** Name1, Name2, Name3

### Context
[What situation led to this decision being needed]

### Decision
[Clear, unambiguous statement of what was decided]

### Rationale
[Why this decision was made - the reasoning]

### Alternatives Considered
1. **Option A:** [Description] - Rejected because [reason]
2. **Option B:** [Description] - Rejected because [reason]

### Implications
- [Consequence 1]
- [Consequence 2]

### Action Required
- [ ] [Action item with owner and deadline]

Action Item Standard

Action Item Classification

Priority	Response Time	Characteristics
`critical`	Within 24 hours	Blocks other work, external commitment, legal/compliance
`high`	Within 1 week	Important milestone, stakeholder expectation
`medium`	Within 2 weeks	Supports ongoing work, no hard deadline
`low`	When convenient	Nice to have, optimization

Action Item Format

## Action Item: [AI-YYYYMMDD-XXX]

**Action:** [Specific, measurable action]
**Owner:** [Name]
**Deadline:** [Date or timeframe]
**Priority:** [critical|high|medium|low]
**Dependencies:** [List any blocking items]
**Status:** [pending|in_progress|completed|blocked]
**Notes:** [Any additional context]

MoE Analysis Pipeline

For complex meetings, use Mixture of Experts analysis:

Stage 1: Expert Extraction (Parallel)

Expert	Focus	Output
Strategic Analyst	Business implications, competitive positioning	Strategic decisions summary
Legal Reviewer	Contracts, agreements, compliance, risk	Legal obligations/concerns
Technical Architect	Technical decisions, architecture implications	Technical decision log
Operations Coordinator	Action items, timelines, dependencies	Action item tracker
Relationship Manager	Stakeholder sentiment, relationship dynamics	Stakeholder analysis

Stage 2: Synthesis

Combine expert outputs into unified meeting summary with:

Executive summary (3-5 bullet points)
Decision log (all decisions with rationale)
Action item tracker (with assignments)
Strategic implications
Risk register (concerns and mitigations)

Stage 3: Validation

Cross-check decisions against action items
Verify all action items have owners
Confirm deadlines are realistic
Flag any contradictions or gaps

Output Formats

1. Executive Summary (for leadership)

# Meeting Summary: {Title}
**Date:** YYYY-MM-DD | **Type:** {type} | **Duration:** XX min

## Key Outcomes
- {Bullet 1: Most important decision/outcome}
- {Bullet 2: Second most important}
- {Bullet 3: Third most important}

## Decisions Made
| Decision | Owner | Impact |
|----------|-------|--------|
| {Decision 1} | {Name} | {HIGH/MEDIUM/LOW} |

## Action Items (by Priority)
| Action | Owner | Deadline |
|--------|-------|----------|
| {Critical action} | {Name} | {Date} |

## Next Steps
1. {Immediate next step}
2. {Follow-up meeting if needed}

2. Full Analysis (for reference)

Use MEETING-ANALYSIS-TEMPLATE.md

3. JSONL Export (for database/context)

{
  "type": "meeting_analysis",
  "meeting_id": "MTG-YYYYMMDD-XXX",
  "date": "YYYY-MM-DD",
  "participants": ["name1", "name2"],
  "decisions": [...],
  "action_items": [...],
  "topics": [...],
  "summary": "..."
}

Integration Points

Context System (`/cx`, `/cxq`)

Meeting analyses are automatically indexed into context system:

Decisions queryable via /cxq --decisions
Action items trackable via TodoWrite
Searchable by participant, topic, date

Task Tracking

Action items extracted from meetings can be:

Added to PILOT plan
Synced to cloud task tracking
Linked to session messages

Calendar/Follow-up

Generated action items can trigger:

Follow-up meeting scheduling
Deadline reminders
Status check-ins

Compliance Requirements

Retention

Meeting analyses retained for minimum 7 years
Decision rationale preserved for audit trail
Versioning for any amendments

Privacy

PII handling per data classification
Recording consent documented
Distribution controls per sensitivity

Audit Trail

All analyses include source document reference
Modifications tracked with timestamps
Analyst attribution maintained

Component	Path	Purpose
Agent	`agents/meeting-notes-analyzer.md`	AI agent for meeting analysis
Skill	`skills/meeting-analysis-patterns/SKILL.md`	Reusable analysis patterns
Command	`commands/analyze-meeting.md`	`/analyze-meeting` invocation
Template	`coditect-core-standards/TEMPLATES/MEETING-ANALYSIS-TEMPLATE.md`	Output template
Script	`scripts/meeting-analyzer.py`	Batch processing script
Workflow	`workflows/meeting-analysis-workflow.md`	End-to-end workflow
Hook	`hooks/post-meeting-analysis-hook.py`	Post-analysis automation

Changelog

Version	Date	Author	Changes
1.0.0	2026-01-13	CODITECT	Initial standard

Compliance: CODITECT-STANDARD-MEETING-ANALYSIS v1.0.0 Owner: AZ1.AI INC | CODITECT Core Standards Team

Purpose​

Meeting Analysis Framework​

1. Document Classification​

2. Required Extraction Elements​

3. Analysis Quality Criteria​

Decision Documentation Standard​

Decision Severity Classification​

Decision Documentation Format​

Action Item Standard​

Action Item Classification​

Action Item Format​

MoE Analysis Pipeline​

Stage 1: Expert Extraction (Parallel)​

Stage 2: Synthesis​

Stage 3: Validation​

Output Formats​

1. Executive Summary (for leadership)​

2. Full Analysis (for reference)​

3. JSONL Export (for database/context)​

Integration Points​

Context System (/cx, /cxq)​

Task Tracking​

Calendar/Follow-up​

Compliance Requirements​

Retention​

Privacy​

Audit Trail​

Related Components​

Changelog​