weekly-retro

# Weekly Retro Part of the Personal Corp framework — running a one-person business through AI agents. Structured weekly retrospective. Gather facts from code and project management tools, interview the founder, capture findings into issues and canonical files. ## Setup Before first use, define these in your project's `CLAUDE.md`: ```markdown ## Weekly Retro Config ### Repos to scan List all repos the agent should check for commits: - ~/Projects/main-app - ~/Projects/marketing-site - ~/Projects/docs ### GitHub owner Your GitHub username or org for issue search: - owner: your-github-handle ### GitHub Project ID Project board where retro issues land: - project_id: 7 ### Canonical files (single source of truth) Files that hold authoritative data — agent must check these before writing numbers: - data.md — prices, revenue, historical totals - product.md — current offers - insights.md — strategic conclusions ### Retro log path Where retro artifacts are saved. Two files per retro live here: - `WNN.md` — interview log + final summary - `WNN-outcomes.md` — outcomes scorecard (planned outcomes vs evidence) Example: - retro_log_path: docs/retro/ ### Task routing Map task types to repos so issues land in the right place: | Type | Repo | |------|------| | Backend bugs | main-app | | Marketing | marketing-site | | Strategy, cross-cutting | project-brain | ### Interview topics (customize to your business) Ordered list of areas to cover: 1. Product delivery 2. Sales / pipeline 3...