e2932d1d84
Skills Created: - outline: Full MCP integration with Outline wiki (search, read, create, export, AI queries) - Enhanced basecamp: Added project mapping configuration to PARA structure - Enhanced daily-routines: Integrated work context (Basecamp, Outline) into daily/weekly workflows - Enhanced meeting-notes: Added Teams transcript processing workflow guide PARA Work Structure Created: - 01-projects/work/: 10 project folders with MOCs (placeholders for user customization) - 02-areas/work/: 5 area files (current-job, professional-dev, team-management, company-knowledge, technical-excellence) - 03-resources/work/wiki-mirror/: Ready for Outline exports - 04-archive/work/: Ready for completed work Documentation Added: - skills/outline/SKILL.md: Comprehensive wiki workflows and tool references - skills/outline/references/outline-workflows.md: Detailed usage examples - skills/outline/references/export-patterns.md: Obsidian integration patterns - skills/meeting-notes/references/teams-transcript-workflow.md: Manual DOCX → meeting note workflow - skills/chiron-core/references/work-para-structure.md: Work-specific PARA organization Key Integrations: - Basecamp ↔ Obsidian: Project mapping and task sync - Outline ↔ Obsidian: Wiki search, export decisions, knowledge discovery - Teams → Obsidian: Transcript processing with AI analysis - All integrated into daily/weekly routines Note: n8n workflows skipped per user request. Ready for n8n automation later.
44 lines
1.4 KiB
Markdown
44 lines
1.4 KiB
Markdown
---
|
|
name: chiron-meeting
|
|
description: "Meeting notes - structured capture of meetings with action items"
|
|
---
|
|
|
|
# Meeting Notes
|
|
|
|
Take structured meeting notes with action item extraction.
|
|
|
|
## Steps
|
|
|
|
1. **Parse meeting request**:
|
|
- Meeting title (if provided)
|
|
- Attendees (if mentioned)
|
|
- Meeting type (standup, 1:1, workshop, decision)
|
|
2. **Create meeting note** using template from `~/CODEX/_chiron/templates/meeting.md`:
|
|
- Location: `~/CODEX/01-projects/[project]/meetings/[topic]-YYYYMMDD.md` (if project-specific)
|
|
- Or `~/CODEX/00-inbox/meetings/[topic]-YYYYMMDD.md` (if general)
|
|
3. **Fill in sections**:
|
|
- Title, date, time, location
|
|
- Attendees and roles
|
|
- Notes (if user provides or if meeting in progress)
|
|
- Decisions made
|
|
- Action items (extract from notes or user-provided)
|
|
4. **Create action item tasks** in Obsidian Tasks format with owners and due dates
|
|
5. **Link to context** (project or area)
|
|
|
|
## Expected Output
|
|
|
|
Meeting note created with:
|
|
- Proper frontmatter (date, attendees, tags)
|
|
- Attendees list
|
|
- Notes section
|
|
- Decisions section
|
|
- Action items in Obsidian Tasks format with @mentions and due dates
|
|
- Links to related projects/areas
|
|
|
|
## Related Skills
|
|
|
|
- `meeting-notes` - Core meeting workflow and templates
|
|
- `task-management` - Action item extraction and task creation
|
|
- `obsidian-management` - File operations and template usage
|
|
- `project-structures` - Project meeting placement
|