From granola-pack
Integrate Granola meeting notes into your local development workflow. Use when setting up development workflows, accessing notes programmatically, or syncing meeting outcomes with project tools. Trigger with phrases like "granola dev workflow", "granola development", "granola local setup", "granola developer", "granola coding workflow".
How this skill is triggered — by the user, by Claude, or both
Slash command
/granola-pack:granola-local-dev-loopThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Integrate Granola meeting notes into your local development workflow for seamless project management.
Integrate Granola meeting notes into your local development workflow for seamless project management.
Configure automatic export of meeting notes:
Create a local directory for meeting notes:
# Create meeting notes directory
mkdir -p ~/dev/meeting-notes
# Create sync script
cat > ~/dev/scripts/sync-granola-notes.sh << 'EOF'
#!/bin/bash
# Sync Granola notes to local project
NOTES_DIR="$HOME/dev/meeting-notes"
PROJECT_DIR="$1"
if [ -z "$PROJECT_DIR" ]; then
echo "Usage: sync-granola-notes.sh <project-dir>"
exit 1
fi
# Copy relevant notes to project docs
cp -r "$NOTES_DIR"/*.md "$PROJECT_DIR/docs/meetings/" 2>/dev/null
echo "Synced meeting notes to $PROJECT_DIR/docs/meetings/"
EOF
chmod +x ~/dev/scripts/sync-granola-notes.sh
# Add meeting notes to .gitignore if sensitive
echo "docs/meetings/*.md" >> .gitignore
# Or track action items only
cat > docs/meetings/README.md << 'EOF'
# Meeting Notes
Action items and decisions from team meetings.
Full notes available in Granola app.
EOF
#!/usr/bin/env python3
# extract_action_items.py
import re
import sys
def extract_actions(note_file):
with open(note_file, 'r') as f:
content = f.read()
# Find action items section
actions = re.findall(r'- \[ \] (.+)', content)
for action in actions:
print(f"TODO: {action}")
if __name__ == "__main__":
extract_actions(sys.argv[1])
1. Attend sprint planning meeting
Granola captures notes automatically
2. Notes sync to local directory
~/dev/meeting-notes/2025-01-06-sprint-planning.md # 2025 year
3. Extract action items
python extract_action_items.py notes/sprint-planning.md
4. Create tickets automatically
./create-tickets.sh TODO.md
5. Reference in commits
git commit -m "feat: implement login - per meeting 2025-01-06"
| Error | Cause | Solution |
|---|---|---|
| Sync Failed | Zapier disconnected | Reconnect Zapier integration |
| Notes Not Appearing | Export delay | Wait 2-5 minutes after meeting |
| Parsing Errors | Note format changed | Update extraction regex |
| Permission Denied | Directory access | Check file permissions |
Proceed to granola-sdk-patterns for advanced Zapier automation patterns.
Basic usage: Apply granola local dev loop to a standard project setup with default configuration options.
Advanced scenario: Customize granola local dev loop for production environments with multiple constraints and team-specific requirements.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin granola-pack