Generate a comprehensive meeting prep document for the upcoming biweekly meeting.
Data Sources to Analyze
Note: On macOS, date -d is not supported. For "2 weeks ago" use:
python3 -c "from datetime import datetime, timedelta; print((datetime.now()-timedelta(days=14)).strftime('%Y-%m-%d'))"
- •Git Activity (since last meeting)
bash
# Get commits since last meeting date (2 weeks ago)
git log --since="2 weeks ago" --pretty=format:"%h - %s (%an, %ar)" --no-merges
# Get changed files
git diff --name-status HEAD@{2.weeks.ago}..HEAD
- •Completed Issues (closed since last meeting)
bash
gh issue list --state closed --search "closed:>=$(date -d '2 weeks ago' +%Y-%m-%d)"
- •
Active Experiments (current work)
- •Find the latest or active experiment in
experiments/(e.g. highest NNN or the one the user is working on) - •Check that experiment’s README.md and
results/ - •Check for new figures
- •Find the latest or active experiment in
- •
Open Issues (blockers and priorities)
bash
gh issue list --state open --label "priority:high,priority:medium"
- •Library Changes (if applicable)
bash
cd ../../libraries/[library-name] git log --since="2 weeks ago" --pretty=format:"%h - %s" gh pr list --state all --search "updated:>=$(date -d '2 weeks ago' +%Y-%m-%d)" cd -
- •Test Results (quality metrics)
- •Run test suite and capture summary
- •Note any failing or skipped tests
Output Format
Generate a markdown file with this structure:
markdown
# Meeting Prep: [Date] **Meeting Date**: [YYYY-MM-DD] **Period Covered**: [Last Meeting Date] to [Today] **Prepared By**: Claude + [Your Name] --- ## Executive Summary [2-3 sentence overview of progress and key points] --- ## Progress Since Last Meeting ### Experiments Completed [For each completed experiment:] - **Experiment**: [Name/Number] - **Goal**: [What you were testing] - **Key Results**: [Bullet points] - **Figures**: [Links to generated figures] - **Status**: ✅ Complete | ⚠️ Needs Discussion | 🔄 Ongoing ### Code Changes #### Library Updates - [List library commits with brief description] - [Link to merged or open PRs] #### Project Code - [List significant project commits] ### Issues Closed [For each closed issue:] - #[number]: [title] ([CATEGORY]) - [Brief description of what was done] - [Link to commits or PRs] --- ## Current Status ### Active Work **Current Experiment**: [experiments/NNN-name/] - **Objective**: [What you're working on] - **Progress**: [Percentage or milestone] - **Blockers**: [Any issues] ### Recent Results [Highlight interesting findings:] - [Result 1 with interpretation] - [Result 2 with interpretation] ### Code Quality - **Tests Passing**: [X/Y] (XX%) - **Known Issues**: [Any test failures] --- ## Blockers & Challenges ### Technical Blockers [Issues preventing progress] ### Scientific Questions [Questions needing discussion] ### Resource Needs [HPC time, data, tools needed] --- ## Plans for Next Period ### Immediate Priorities (Next 2 Weeks) 1. [Task 1] - Issue #[number] 2. [Task 2] - Issue #[number] ### Proposed Experiments [New experiments to discuss] ### Library Development Needs [Features needed in library] --- ## Discussion Topics ### For Advisor Feedback 1. [Specific question 1] 2. [Specific question 2] ### Decisions Needed - [Decision point 1] - [Decision point 2] --- ## Appendix ### Detailed Commit Log
[Full git log]
code
### Open Issues by Priority [List with links] ### Figures Generated This Period [List with brief captions]
Execution Strategy
- •Gather data from all sources
- •Analyze patterns - group related commits
- •Synthesize - explain the narrative
- •Highlight items needing discussion
- •Cross-reference issues to commits to results
- •Be honest - include setbacks
Quality Checks
- • All issue numbers link correctly
- • Figure paths exist
- • Commit hashes are valid
- • Timeline is accurate
- • Blockers are clearly stated
- • Questions are specific
- • Next steps are concrete
Save output to meetings/prep/YYYY-MM-DD-prep.md