strategy-weeklylisted

**Version**: 1.0 **Created**: 2026-03-23 **Last Updated**: 2026-03-23 **Authors:** Ömer Ufuk --- # /strategy-weekly — Weekly Tactical Strategy Sync **Usage**: `/strategy-weekly` or `/strategy-weekly $ARGUMENTS` ## Current State - Strategy docs: !`ls strategy-output/*.md 2>/dev/null | wc -l | tr -d ' '` files in strategy-output/ - Recent commits: !`git log --oneline -5 2>/dev/null` - Last weekly report: !`ls -t tasks/weekly/*.md 2>/dev/null | head -1` **Examples**: ``` /strategy-weekly # full weekly sync — spawns growth-lead, produces brief /strategy-weekly --dry-run # assessment only, no file output ``` --- ## What This Command Does Runs a lightweight weekly strategy sync that answers three questions: What shipped? What is the growth status? What should we focus on next week? Spawns the growth-lead agent for channel/content assessment, cross-references shipped work against the sprint plan, and produces a 1-page tactical brief saved to `tasks/weekly/`. --- ## Execution Instructions When this command is invoked, execute the following steps in order. --- ### Step 1 — Verify Prerequisites Check that strategy documents exist: ```bash ls strategy-output/*.md 2>/dev/null | wc -l ``` If zero files found, stop: "No strategy-output/ directory found. This skill requires a strategy package." Check that the `tasks/weekly/` directory exists, create if not: ```bash mkdir -p tasks/weekly ``` --- ### Step 2 — Gather Shipped Work Read the git log since the l