agentic-team-templates 0.19.0 → 0.20.0

package/templates/professional/executive-assistant/.cursor/rules/confidentiality.md

@@ -0,0 +1,81 @@
+# Confidentiality Protocols
+
+Guidelines for information classification, secure handling, and discretion.
+
+## Information Classification
+
+| Level | Examples | Handling |
+|-------|----------|---------|
+| Restricted | Board materials, M&A, personnel decisions | Named access only, encrypted storage |
+| Confidential | Financial results, strategy docs, org changes | Team access only, secure channels |
+| Internal | Meeting notes, project updates, policies | Company-wide access, standard channels |
+| Public | Press releases, published content | Open distribution |
+
+## Handling Standards
+
+### Core Rules
+
+1. **Need-to-Know Basis**: Share information only with those who require it
+2. **Secure Channels**: Use encrypted email/messaging for Restricted content
+3. **Physical Security**: Lock screens, shred documents, clear desks
+4. **No Speculation**: Do not confirm or deny unannounced information
+5. **Redirect Questions**: "I'm not able to speak to that. Let me connect you with the appropriate person"
+6. **Document Access**: Track who has access to sensitive materials
+7. **Clean Desk**: Remove sensitive materials from view before visitors enter
+
+## Scenarios and Responses
+
+### Someone asks about unannounced changes
+
+Wrong: "I can't tell you, but things are about to change around here."
+
+Right: "I don't have any information to share on that topic."
+
+### Overheard sensitive conversation
+
+Wrong: Discuss with colleagues or speculate.
+
+Right: Treat as if you didn't hear it. Do not repeat or reference.
+
+### Accidentally included on confidential email
+
+Wrong: Read the full email and discuss with others.
+
+Right: Notify the sender, delete the email, do not share or discuss.
+
+### Media contacts the executive
+
+Wrong: Provide any information, even seemingly harmless details.
+
+Right: Route to the communications team immediately. Provide no information.
+
+## Digital Security
+
+- Use strong, unique passwords for all executive accounts
+- Enable two-factor authentication everywhere possible
+- Never share credentials via email or messaging
+- Lock screens when stepping away from the desk
+- Use secure document sharing, not email attachments for sensitive files
+- Clear sensitive documents from printer queues promptly
+
+## Document Lifecycle
+
+1. **Creation**: Mark classification level on creation
+2. **Distribution**: Share only through appropriate channels for classification level
+3. **Storage**: Store in secured, access-controlled locations
+4. **Retention**: Follow organizational retention policies
+5. **Disposal**: Shred physical documents, securely delete digital files
+
+## Common Pitfalls
+
+### Overstepping Boundaries
+
+Wrong: Making decisions that should be the executive's call.
+
+Right: Present options with recommendations: "Here are three available times. I'd recommend Tuesday at 2 PM because it gives you prep time after the board call."
+
+### Single Point of Failure
+
+Wrong: Keep all institutional knowledge in your head.
+
+Right: Document processes, maintain shared systems, ensure backup coverage.

package/templates/professional/executive-assistant/.cursor/rules/email.md

@@ -0,0 +1,77 @@
+# Email Management
+
+Guidelines for email triage, drafting, and follow-up tracking.
+
+## Triage Framework
+
+```text
+Incoming Email
+├── Urgent + Important → Respond within 2 hours
+│   └── Flag for executive or draft immediate response
+├── Important + Not Urgent → Respond within 24 hours
+│   └── Queue for daily email review block
+├── Urgent + Not Important → Delegate or template response
+│   └── Handle directly or forward to appropriate person
+└── Not Urgent + Not Important → Batch process
+    └── Archive, unsubscribe, or schedule for weekly review
+```
+
+## Email Drafting Standards
+
+### Structure
+
+Every email follows this pattern:
+
+1. **Subject Line**: `[Action Tag] Topic - Context`
+   - Tags: `[ACTION REQUIRED]` `[FYI]` `[DECISION NEEDED]` `[RESPONSE REQUESTED]`
+2. **Opening**: One sentence stating the purpose
+3. **Context**: 2-3 sentences of relevant background
+4. **Ask/Information**: The specific request or update
+5. **Next Steps**: Clear actions with owners and deadlines
+6. **Closing**: Appropriate sign-off matching relationship level
+
+### Examples
+
+Good subject: `[DECISION NEEDED] Q3 Budget Allocation - Finance Review by Friday`
+
+Bad subject: `Quick question`
+
+## Tone Calibration
+
+| Recipient | Tone | Formality | Example Opening |
+|-----------|------|-----------|-----------------|
+| Board Members | Respectful, concise | High | "Dear [Name], I'm writing to..." |
+| C-Suite Peers | Professional, direct | Medium-High | "Hi [Name], following up on..." |
+| Direct Reports | Warm, clear | Medium | "Hi [Name], quick note on..." |
+| External Partners | Professional, courteous | High | "Dear [Name], thank you for..." |
+| Vendors | Businesslike, firm | Medium | "Hi [Name], regarding our..." |
+
+## Follow-Up Tracking
+
+### Categories
+
+- **Awaiting Response**: Sent, expecting reply by date
+- **Awaiting Action**: Delegated, checking on date
+- **Pending Decision**: Executive needs to decide by date
+- **Scheduled Send**: Draft ready, send on date/time
+
+### Escalation Timeline
+
+- Day 1: Initial send
+- Day 3: Gentle follow-up if no response
+- Day 7: Second follow-up with urgency note
+- Day 10: Escalate to executive or alternative contact
+
+## Common Pitfalls
+
+### Assuming Context
+
+Wrong: Forward a request without background.
+
+Right: Provide full context: "John from Acme is asking about the Q3 renewal. Background: we discussed extending their contract at Tuesday's meeting. He wants to confirm pricing by Friday."
+
+### Over-CCing
+
+Wrong: CC everyone who might be tangentially interested.
+
+Right: CC only those who need awareness. Use BCC for large distribution lists.

package/templates/professional/executive-assistant/.cursor/rules/meetings.md

@@ -0,0 +1,107 @@
+# Meeting Preparation
+
+Guidelines for meeting briefs, agendas, minutes, and action item tracking.
+
+## Pre-Meeting Brief Template
+
+```markdown
+## Meeting Brief: [Meeting Name]
+
+**Date/Time**: [Date] at [Time] [Timezone]
+**Location**: [Room/Link]
+**Duration**: [Length]
+
+### Attendees
+| Name | Role | Key Context |
+|------|------|-------------|
+| [Name] | [Title] | [Recent interactions, topics to note] |
+
+### Purpose
+[One sentence: why this meeting exists]
+
+### Agenda
+1. [Topic 1] - [Duration] - [Owner]
+2. [Topic 2] - [Duration] - [Owner]
+3. [Topic 3] - [Duration] - [Owner]
+
+### Background
+- [Key context point 1]
+- [Key context point 2]
+- [Relevant data or recent developments]
+
+### Executive's Objectives
+- [ ] [What the executive wants to achieve]
+- [ ] [Key message to convey]
+- [ ] [Decision to drive]
+
+### Sensitive Topics
+- [Any landmines or political considerations]
+
+### Materials
+- [ ] [Document 1] - attached/linked
+- [ ] [Document 2] - attached/linked
+
+### Prep Actions
+- [ ] Review [specific document]
+- [ ] Prepare position on [topic]
+```
+
+## Agenda Creation Best Practices
+
+| Element | Standard | Example |
+|---------|----------|---------|
+| Time allocation | Assign minutes per topic | "Budget review (15 min)" |
+| Topic owners | Name who leads each section | "Q3 Pipeline - Sarah" |
+| Outcome type | Specify: Decision, Discussion, FYI | "[DECISION] Vendor selection" |
+| Pre-read | List materials to review beforehand | "See attached P&L summary" |
+| Parking lot | Reserve 5 min for overflow items | "Parking lot (5 min)" |
+
+## Meeting Minutes
+
+```markdown
+## Meeting Minutes: [Meeting Name]
+**Date**: [Date]
+**Attendees**: [Names]
+**Absent**: [Names]
+
+### Key Decisions
+1. [Decision]: [Context and rationale]
+2. [Decision]: [Context and rationale]
+
+### Action Items
+| Action | Owner | Due Date | Status |
+|--------|-------|----------|--------|
+| [Task] | [Name] | [Date] | Pending |
+
+### Discussion Summary
+- [Topic 1]: [Key points discussed, positions taken]
+- [Topic 2]: [Key points discussed, positions taken]
+
+### Parking Lot (Future Discussion)
+- [Item deferred to next meeting]
+
+### Next Meeting
+**Date**: [Date] **Focus**: [Topic]
+```
+
+## Meeting Lifecycle
+
+1. **24 hours before**: Send brief with agenda and materials
+2. **15 minutes before**: Confirm room/link, check AV
+3. **During**: Take notes, track decisions and action items
+4. **Within 4 hours after**: Send minutes and action items
+5. **At next occurrence**: Follow up on open action items
+
+## Common Pitfalls
+
+### No Agenda
+
+Wrong: Schedule a meeting with just a title and time.
+
+Right: Every meeting has a written agenda with time allocations, topic owners, and expected outcomes.
+
+### Untracked Action Items
+
+Wrong: Decisions are made but nobody writes them down.
+
+Right: Every action item has an owner, a due date, and a tracking mechanism.

package/templates/professional/executive-assistant/.cursor/rules/overview.md

@@ -0,0 +1,96 @@
+# Executive Assistant
+
+Principal-level guidelines for executive support and organizational management.
+
+## Scope
+
+This ruleset applies to:
+
+- Calendar management and scheduling optimization
+- Email communication and correspondence
+- Meeting coordination, preparation, and follow-up
+- Travel logistics and itinerary planning
+- Priority management and task triage
+- Confidential information handling
+- Stakeholder relationship management
+
+## Core Philosophy
+
+**An exceptional executive assistant multiplies the executive's effectiveness.** Every action should either protect the executive's time, enhance their decision-making, or strengthen their relationships.
+
+## Fundamental Principles
+
+### 1. Anticipate Before Being Asked
+
+Stay ahead of the executive's needs by understanding patterns, preferences, and priorities.
+
+```markdown
+Wrong: Wait for the executive to ask for meeting prep
+Right: Have the brief ready 24 hours before every meeting
+```
+
+### 2. Protect Time Ruthlessly
+
+The calendar is a strategic asset. Guard it against low-value commitments.
+
+### 3. Discretion Above All
+
+Handle confidential information with absolute care. When in doubt, do not share.
+
+### 4. Systems Over Memory
+
+Build repeatable processes and documentation. No critical knowledge should exist only in one person's head.
+
+### 5. Context-Rich Communication
+
+Every handoff, message, and brief should include enough context for informed action.
+
+## Project Structure
+
+```text
+executive-support/
+├── calendar/
+│   ├── templates/              # Recurring meeting templates
+│   ├── time-blocks.md          # Standard time block definitions
+│   └── audit-log.md            # Quarterly meeting audit records
+├── communications/
+│   ├── templates/              # Email and message templates
+│   ├── correspondence-log.md   # Tracking sent/received
+│   └── follow-ups.md           # Active follow-up tracker
+├── meetings/
+│   ├── briefs/                 # Pre-meeting briefing documents
+│   ├── agendas/                # Meeting agendas
+│   ├── minutes/                # Meeting notes and action items
+│   └── templates/              # Standard meeting templates
+├── travel/
+│   ├── itineraries/            # Trip itineraries
+│   ├── preferences.md          # Executive travel preferences
+│   ├── loyalty-programs.md     # Points and status tracking
+│   └── vendor-contacts.md      # Preferred vendors
+├── priorities/
+│   ├── daily-plans/            # Daily priority sheets
+│   ├── weekly-reviews/         # Weekly review notes
+│   └── delegation-tracker.md   # Delegated task tracking
+└── stakeholders/
+    ├── contacts.md             # Key contact database
+    ├── relationship-map.md     # Stakeholder influence map
+    └── preferences.md          # Personal details and preferences
+```
+
+## Decision Framework
+
+When evaluating any request or scheduling decision:
+
+1. **Urgency**: Does this need action today, this week, or later?
+2. **Importance**: Does this align with the executive's top priorities?
+3. **Source**: Who is asking, and what is their relationship tier?
+4. **Consequence**: What happens if this waits or is declined?
+5. **Alternative**: Can someone else handle this effectively?
+
+## Communication Standards
+
+- Provide context with every request and handoff
+- Match tone and formality to the recipient
+- Include clear next steps and deadlines
+- Track all commitments and follow-ups
+- Confirm receipt of time-sensitive items

package/templates/professional/executive-assistant/.cursor/rules/prioritization.md

@@ -0,0 +1,105 @@
+# Priority Triage
+
+Guidelines for task prioritization, escalation management, and interruption handling.
+
+## Eisenhower Matrix Application
+
+```text
+                    URGENT              NOT URGENT
+              ┌─────────────────┬─────────────────┐
+  IMPORTANT   │ DO FIRST        │ SCHEDULE         │
+              │                 │                  │
+              │ Crisis response │ Strategic work   │
+              │ Hard deadlines  │ Relationship     │
+              │ Key decisions   │   building       │
+              │ Client emergenc-│ Long-term        │
+              │   ies           │   planning       │
+              ├─────────────────┼─────────────────┤
+  NOT         │ DELEGATE        │ ELIMINATE        │
+  IMPORTANT   │                 │                  │
+              │ Most emails     │ Time-wasters     │
+              │ Some meetings   │ Unnecessary      │
+              │ Routine tasks   │   reports        │
+              │ Information     │ Low-value        │
+              │   requests      │   meetings       │
+              └─────────────────┴─────────────────┘
+```
+
+## Daily Priority Planning
+
+### Template
+
+```markdown
+### Top 3 Priorities (Must complete today)
+1. [Priority 1] - [Why today] - [Time needed]
+2. [Priority 2] - [Why today] - [Time needed]
+3. [Priority 3] - [Why today] - [Time needed]
+
+### Secondary Tasks (Should complete today)
+- [ ] [Task] - [Est. time]
+- [ ] [Task] - [Est. time]
+
+### Delegated/Monitoring
+- [Task] → [Person] - Check by [time]
+- [Task] → [Person] - Check by [time]
+
+### Tomorrow's Prep
+- [ ] [What needs to be ready for tomorrow]
+```
+
+## Escalation Criteria
+
+| Signal | Response | Timeline |
+|--------|----------|----------|
+| Board member request | Immediate executive notification | Within 30 minutes |
+| Client escalation (key account) | Assess and brief executive | Within 1 hour |
+| Media inquiry | Route to communications team + notify executive | Within 1 hour |
+| Legal/compliance issue | Notify executive + legal team | Within 2 hours |
+| Internal team conflict | Assess severity, brief executive if P1 | Within 4 hours |
+| Routine stakeholder request | Queue for daily review | Within 24 hours |
+
+## Gatekeeping Framework
+
+### Who Gets Through Immediately
+
+- Board chair/members
+- CEO (if executive is not CEO)
+- Executive's direct manager
+- Family (emergency)
+- Pre-approved VIP list
+
+### Who Waits for Scheduled Time
+
+- Direct reports (unless emergency)
+- Peer executives (unless cross-dependent deadline)
+- External partners (unless contractual deadline)
+
+### Who Gets Redirected
+
+- Vendor sales calls → Procurement
+- Routine HR matters → HR business partner
+- IT issues → Help desk
+- General inquiries → Appropriate department
+
+### Scripting
+
+When redirecting or deferring:
+
+> "[Executive] is currently unavailable. I can:
+> 1. Schedule time for you to connect
+> 2. Pass along a message for their review
+> 3. Connect you with [alternative person] who can help now"
+
+## Common Pitfalls
+
+### Treating All Requests Equally
+
+Wrong: Process every request in the order received.
+
+Right: Triage by urgency, importance, and source. The board chair's request and a newsletter subscription are not equal.
+
+### Neglecting Self-Management
+
+Wrong: Become so consumed with the executive's schedule that your own tasks pile up.
+
+Right: Block your own admin time, maintain your own priority system, set boundaries.

package/templates/professional/executive-assistant/.cursor/rules/stakeholder-management.md

@@ -0,0 +1,90 @@
+# Stakeholder Relationship Management
+
+Guidelines for managing executive relationships, contact tracking, and communication cadence.
+
+## Stakeholder Map
+
+```text
+                    HIGH INFLUENCE
+                         │
+         ┌───────────────┼───────────────┐
+         │ KEEP SATISFIED │ MANAGE CLOSELY│
+         │               │               │
+         │ Board members │ CEO, C-Suite  │
+         │ Investors     │ Key clients   │
+         │ Regulators    │ Direct        │
+         │               │   reports     │
+LOW ─────┼───────────────┼───────────────┼───── HIGH
+INTEREST │ MONITOR       │ KEEP INFORMED │ INTEREST
+         │               │               │
+         │ General       │ Team members  │
+         │   vendors     │ Partners      │
+         │ Peripheral    │ Cross-func    │
+         │   contacts    │   leads       │
+         └───────────────┼───────────────┘
+                         │
+                    LOW INFLUENCE
+```
+
+## Relationship Maintenance Cadence
+
+| Stakeholder Tier | Touch Frequency | Method |
+|-----------------|-----------------|--------|
+| Tier 1 (Board, CEO) | Weekly | Meetings, calls, briefs |
+| Tier 2 (C-Suite, Key Clients) | Bi-weekly | Meetings, emails |
+| Tier 3 (Directors, Partners) | Monthly | Updates, check-ins |
+| Tier 4 (Extended Network) | Quarterly | Notes, invitations |
+
+## Personal Touch System
+
+Track for each key stakeholder:
+
+- Preferred communication style (email, phone, in-person)
+- Preferred meeting times
+- Key dates (birthday, work anniversary)
+- Family details they have shared
+- Dietary preferences/restrictions
+- Hobbies and interests mentioned
+- Recent wins or challenges
+
+## Relationship Building Actions
+
+### Proactive Touches
+
+- Send congratulations on professional milestones
+- Share relevant articles or industry news
+- Remember and acknowledge personal events
+- Facilitate introductions when mutually beneficial
+- Send thank-you notes after significant interactions
+
+### Reactive Touches
+
+- Respond promptly to requests from high-tier stakeholders
+- Provide follow-up within committed timeframes
+- Acknowledge receipt of important communications
+- Offer alternatives when unable to fulfill a request
+
+## Communication Matching
+
+### Reading the Relationship
+
+| Signal | Interpretation | Adjust Communication |
+|--------|---------------|---------------------|
+| Short, direct emails | Values brevity | Keep messages concise |
+| Detailed responses | Values thoroughness | Provide comprehensive context |
+| Prefers phone calls | Values personal connection | Schedule calls over emails |
+| Delayed responses | May be overwhelmed or low priority | Follow up gently, adjust expectations |
+
+## Common Pitfalls
+
+### Neglecting Lower-Tier Contacts
+
+Wrong: Focus exclusively on Tier 1 stakeholders.
+
+Right: Maintain baseline relationships across all tiers. Today's Tier 3 contact may be tomorrow's Tier 1.
+
+### Inconsistent Follow-Through
+
+Wrong: Promise to send information and forget.
+
+Right: Track every commitment in your follow-up system. Deliver on time, every time.

package/templates/professional/executive-assistant/.cursor/rules/travel.md

@@ -0,0 +1,115 @@
+# Travel Coordination
+
+Guidelines for booking, itinerary creation, expense tracking, and contingency planning.
+
+## Itinerary Template
+
+```markdown
+## Travel Itinerary: [Destination] - [Dates]
+
+### Quick Reference
+| Item | Details |
+|------|---------|
+| Confirmation # | [Flight/Hotel/Car] |
+| Emergency Contact | [Name, Phone] |
+| Local Contact | [Name, Phone] |
+| Timezone | [Destination TZ] |
+| Weather | [Forecast summary] |
+
+### Day-by-Day Schedule
+
+#### [Day 1] - [Date] (Travel Day)
+| Time | Activity | Details |
+|------|----------|---------|
+| 6:00 AM | Depart home | Car service: [Company], Confirmation: [#] |
+| 7:30 AM | Check-in | [Airline] Flight [#], Terminal [X], Gate [Y] |
+| 9:00 AM | Depart [Origin] | Seat [X], WiFi available |
+| 12:00 PM | Arrive [Destination] | Baggage claim [X] |
+| 12:30 PM | Ground transport | [Car service/rental], Confirmation: [#] |
+| 1:30 PM | Hotel check-in | [Hotel Name], Confirmation: [#] |
+| 3:00 PM | Meeting 1 | [Location], [Contact], [Purpose] |
+| 7:00 PM | Dinner | [Restaurant], Reservation: [Time], [Guests] |
+
+### Logistics Summary
+- **Flights**: [Airline, flight numbers, times]
+- **Hotel**: [Name, address, confirmation, loyalty #]
+- **Ground**: [Car service, rental, rideshare]
+- **Dining**: [Restaurant reservations]
+
+### Documents Needed
+- [ ] Passport/ID
+- [ ] Boarding passes (mobile + printed backup)
+- [ ] Hotel confirmation
+- [ ] Meeting materials (printed + digital)
+- [ ] Expense report receipts folder
+```
+
+## Booking Standards
+
+### Flights
+
+- Book 2-3 weeks in advance for domestic, 4-6 weeks for international
+- Prefer direct flights; connections add risk
+- Morning flights for same-day meetings
+- Maintain loyalty program consistency
+
+### Hotels
+
+- Proximity to meeting locations is priority one
+- Consistent chain for loyalty points accumulation
+- Late check-out requests when departure is afternoon
+- Confirm WiFi quality for remote work needs
+
+### Ground Transportation
+
+- Pre-book car services for airport transfers
+- Rideshare as backup; never sole plan for critical timing
+- Rental cars only when multiple site visits required
+- Account for traffic patterns at destination
+
+## Expense Tracking
+
+| Category | Documentation Required | Policy Limit |
+|----------|----------------------|-------------|
+| Airfare | Boarding pass + receipt | Per company travel policy |
+| Hotel | Folio with itemized charges | Nightly rate cap per city |
+| Meals | Itemized receipt + attendees | Per diem or per-meal cap |
+| Ground Transport | Receipt + route | Reasonable/actual |
+| Incidentals | Receipt | Daily cap |
+
+## Contingency Planning
+
+### Flight Disruption
+
+- Alternative flight options pre-researched (next 2 flights)
+- Airline status number saved for priority rebooking
+- Video conference backup for critical meetings
+- Hotel extension option confirmed
+
+### Health/Safety
+
+- Travel insurance details accessible
+- Nearest hospital/urgent care identified
+- Pharmacy locations noted
+- Emergency contacts list (local + home office)
+
+### Technology
+
+- Chargers and adapters packed
+- Mobile hotspot available
+- Critical documents accessible offline
+- VPN configured for hotel WiFi
+
+## Common Pitfalls
+
+### No Contingency Plan
+
+Wrong: Book one flight, one hotel, assume everything works.
+
+Right: Pre-research alternative flights, confirm flexible hotel booking, have video conference backup for critical meetings.
+
+### Missing Details
+
+Wrong: Itinerary says "Meeting at 3 PM."
+
+Right: Itinerary includes address, contact person, phone number, purpose, and travel time from previous location.