strategy-self-critique

To run a red-team critique, aggregate data from strategy, learnings, weekly reviews, retention metrics, and experiments to stress-test assumptions against failure modes and market signals. The output is a formal critique written to strategy/critique.md to guide planning.

A monthly strategy critique is a red-team process that surfaces untested assumptions and risks by analyzing failure modes against market data. You need it during monthly planning cycles to prevent strategy blind spots from derailing your quarterly goals.

Required inputs include strategy/strategy.md, strategy/learnings.md, reviews/weekly/*, metrics/retention/*, and experiments/archive/*. The critique aggregates these files to analyze failure modes and inform quarterly planning decisions.

Yes, the monthly red-team critique is explicitly designed to inform quarterly planning. By surfacing the riskiest assumptions and writing them to strategy/critique.md, leadership receives hard conclusions for decision-making.

The critique integrates retention metrics and experiment archives to stress-test current strategy against market signals and failure modes. It pushes for hard conclusions by revealing the riskiest assumptions across monthly planning cycles.

This critique relies on existing files like strategy/learnings.md and reviews/weekly/*, so it cannot surface risks if those inputs are missing or outdated. It functions best when integrated across monthly planning cycles with continuous data.