← ClaudeAtlas

monthly-reportlisted

Generate monthly board reports. Collects data from Apple Notes, Fireflies, Gmail, and documents, then synthesizes into formatted report. Use when asked to prepare monthly board update or monthly report.
smorrel1/claude-code-skills · ★ 2 · Data & Documents · score 65
Install: claude install-skill smorrel1/claude-code-skills
# Monthly Board Report Generation Multi-phase workflow to generate comprehensive monthly board reports. **Note:** This is a personal workflow skill with configurable paths. Copy `config.example.py` to `config.py` and customize for your environment. ## Overview | Phase | Description | |-------|-------------| | 0 | **READ `FEEDBACK_LOG.md`** before doing anything else | | 1 | Data Collection (Notes, Fireflies, Zoom Docs, Gmail) | | 1c | Engineering retro via gstack `/retro global <N>d` | | 1d | Strategic diagnostic via gstack `/office-hours` (diagnose mode) | | 2 | Context Setup (auto-managed per run) | | 3 | User Confirmation (dates, sections) | | 4 | Parallel Agent Processing (source agents — use Haiku for cheap extraction) | | 5 | Report Generation: three-page main + ~10-page appendix, branded DOCX, never overwrite prior version | ## Phase 0: Read the feedback log `FEEDBACK_LOG.md` in this skill folder is a running record of the user's corrections on prior reports. Read it first. Apply every standing item (structure, branding, deletions, framing). Append a fresh dated section after each new round of feedback; never rewrite old entries. ## Standing process notes (apply every run) These are non-negotiable. If you find yourself about to do otherwise, stop and re-read. - **Read `FEEDBACK_LOG.md` in the monthly-report skill before drafting.** Standing items are captured there. - **Run the `humanizer` skill on the report prose, then PROVE it with the checker.** This is a