weekly-review

Weekly Review

Generic chassis variant. If a private operating repo (e.g. your own growth-os) defines a command with this name, that version is canonical for that repo's data.

Run an honest weekly review across the whole motion — both sides of the bowtie.

Left side (demand → close):

1. Read the last seven entries in ops/daily-log.md.
2. Summarize the week: what shipped, what stalled, any pattern worth naming. Read each channel or effort by the quality of relationships it surfaced, not only headline volume — one deep, high-fit relationship can be the whole return on an effort that looks thin by the numbers.
3. Clear the loop: surface any open MARKETING-ACTION lines in ops/feedback-log.md that haven't been acted on.

Right side (post-sale — read ops/customers.md):

1. Renewals due in the next 30 / 60 / 90 days. Flag any inside 60 days — that's when the renewal motion starts (not day 85).
2. Accounts at risk. List anything at 🔴/🟡 — usage down, champion quiet, single-threaded — and the next step for each.
3. Adoption stalls. Accounts stuck between onboarding and live (a workflow never turned on, a setup step blocking them).
4. Expansion candidates. Healthy accounts ready to grow — hand to sales with the CS context.
5. Top roadmap signals. The highest-priority items in ops/roadmap-signals.md — what product should hear, and anything shipped that still needs its buyer-facing line.

Then:

1. Ownership read. For each live area on both sides, check it has an owner who treats the number as theirs — not just what moved this week. An area no one owns is the pattern to fix first.
2. Chokepoint read (ops/chokepoints.md). Walk the short list of narrow dependencies most of the revenue flows through. Two questions: has anything changed hands or become more concentrated this week, and does every row still have a named owner? A row carried unresolved for 3+ reviews is re-rated, not dropped — sitting there longer earns more attention, not less. Use the same list as a news filter: market noise touching nothing on it gets no time in this review.
3. Pick next week's single most important priority and write it to the top of ops/priorities.md.
4. Name one thing to stop doing — and write the sentence that makes it a prune. Removal is fast and visible while building is slow and invisible, so teams drift toward cutting and call it discipline. Before anything comes off: "this is cut so that X specifically improves, measured by Y, checked on <date>." No sentence, no cut. Log the check date and read it when it arrives — an unverified cut is a dismantling, not a prune.

Lead with the summary. Don't pad it. If ops/customers.md or ops/roadmap-signals.md is empty, say so and skip that section. Reconcile the pipeline mirror against the CRM per .claude/rules/crm-usage.md — read-only beyond what the daily rituals already persisted.