prompts/sunday-digest.md
# DW Overnight Digest — Sunday 6pm **You are running headless — output the digest as plain text/markdown to stdout. Do NOT attempt to use Write/Edit/Read tools or any filesystem operations; the wrapper script captures your stdout and handles the file. Do not include any meta-commentary about tool failures, permission blocks, or "write was blocked" notes — just produce the digest body.** Weekly Designer-Wallcoverings + agent-fleet review. Sunday evening, before Steve plans the upcoming week. This is the longer-form sibling of the daily meetings. ## Output structure (markdown — strategic, not operational) ### Top of the page Title: `DW Overnight Digest — <Mon DD YYYY>` One-line state-of-the-shop: live SKU count direction (up/down/flat from last week), main vendor pipelines healthy/stuck/blocked, any incident worth flagging. ### 1. The week in commits Group the last 7 days of git activity (`### DW overnight (last 7 days)` section in context) by theme. Themes will vary — common ones: - **Catalog enrichment** — SKU updates, vendor scrapes finishing, pricing fixes - **Site & UX** — DW theme, viewer changes, design iterations - **Agent infra** — new agents, PM2 stability, watchdog tweaks - **Platform** — secrets manager, MCP, tooling Per theme: 2–4 bullets max, each citing the commit hash + 1-line gist. ### 2. Agent fleet — who earned their keep Top 5 agents by activity (commits, restarts, productive throughput). Bottom 3 (idle, errored, stuck). Don't list all 50+ agents; show signal. ### 3. Inventory of unfinished Open TODOs from the context. Don't repeat the daily-meeting carryover — pick out items that have been hanging for >7 days. These are candidates for either ship or kill. ### 4. Designer-Wallcoverings ops items SKU-side reality checks pulled from the context if available: - Vendors with imports in flight (Brewster, York, Schumacher, etc.) - Pricing inconsistencies surfaced this week - Image gaps (products active without images — there shouldn't be any per the standing rule) If no DW commits this week, say "DW catalog quiet this week — focus was elsewhere." ### 5. Strategic prompt for next week ONE question. Examples: - "Animals directory has 4k listings but no monetization wired up — is next week the week we ship the $499 site upgrade flow, or do we wait for ingest to hit 10k?" - "WhoLivedThere ecosystem has 3 domains scaffolded but only one site-factory pipeline — should domain #2 + #3 share the pipeline or get separate ones?" - "Codex CLI has been quota-blocked all week; is it time to swap the claude-codex skill to dual-Claude debate as the default?" ## Constraints - Total output: 700–1000 words. This is the long-form weekly read; daily meetings are tight. - Cite commits by short hash + project name. - If a section has no real content this week, say so — don't pad. - Address Steve directly in the strategic prompt. - No emoji except ✅ ⚠️ 🚀 for emphasis on real wins/fires. Now produce the digest from the context that follows.