@onion-ai/cli 1.0.0-beta.1

package/framework/commands/f/process-meetings.md

@@ -0,0 +1,103 @@
+---
+name: process-meetings
+description: Process new meeting transcripts and update the engagement tracker
+model: sonnet
+category: general
+tags: [process-meetings, context, preparation]
+version: "1.0.0"
+updated: "2025-12-30"
+---
+# Process Meetings
+
+You are updating the engagement tracker with any new meeting transcripts that haven't been processed yet.
+
+## Your Task
+
+1. **Read the current tracker:** Open `docs/engagement-tracker.md` and understand the current state.
+
+2. **Identify processed meetings:** Look at the "Processed Meetings" section to see which files have already been incorporated.
+
+3. **Scan for new meetings:** List all `.md` files in `docs/meetings/`. Identify any that are NOT listed in "Processed Meetings".
+
+4. **Process new meetings chronologically:** For each unprocessed meeting (sorted by date, oldest first):
+   - Read the full transcript
+   - Extract relevant information
+   - Update the tracker sections
+
+5. **Write the updated tracker:** Save the updated `docs/engagement-tracker.md`.
+
+6. **Report:** Briefly state which meetings were processed, or "No new meetings to process" if none found.
+
+---
+
+## Rules
+
+1. **No double processing** — If a meeting file is already in "Processed Meetings", skip it entirely.
+2. **Chronological order** — Process meetings oldest to newest so the narrative builds correctly.
+3. **Preserve existing content** — Add to the tracker, don't overwrite previous entries unless correcting an error.
+4. **Be concise** — Each entry should be scannable, not verbose.
+5. **Use exact filenames** — In "Processed Meetings", list the filename exactly as it appears in `docs/meetings/`.
+
+---
+
+## How to Update Each Section
+
+### Current Status
+- Update **Last Updated** to today's date
+- Update **Last Meeting** to the most recent meeting processed
+- Update **Engagement Phase** if there's a clear phase transition (Discovery → Negotiation → Onboarding → Active → etc.)
+
+### Timeline
+Add a row for each new meeting:
+```
+| YYYY-MM-DD | Meeting Title | One-line key outcome |
+```
+
+### Decision Log
+Add any decisions made, in reverse chronological order (newest at top):
+```
+- **[YYYY-MM-DD]:** [Decision] — [Brief context or rationale]
+```
+Only add actual decisions, not discussions or possibilities.
+
+### Open Items
+- Add new open items that emerged
+- Mark resolved items by moving them to a "Resolved" subsection or removing them
+- Format: `- [ ] [Item] — [Owner if known] — [Since: YYYY-MM-DD]`
+
+### Next Steps
+Replace this section with the current next steps based on the latest meeting. This section should reflect the NOW, not accumulate history.
+
+### Key Relationships
+Add or update people as they appear:
+```
+- **[Name]** — [Role/Title] — [Stance: Champion / Blocker / Neutral / Decision Maker / Unknown]
+```
+Update stance if it changes based on new information.
+
+### Processed Meetings
+Add each processed file:
+```
+- [x] `filename.md`
+```
+
+---
+
+## Output
+
+After updating the tracker, respond with:
+
+```
+Processed X new meeting(s):
+- filename1.md
+- filename2.md
+
+Key updates:
+- [Brief summary of major additions/changes]
+```
+
+Or if nothing new:
+
+```
+No new meetings to process.
+```