weekly-planning

A structured weekly planning ritual closes the previous week, captures progress, analyzes outcomes, cleans backlogs, and outlines the next week's plan to reduce uncertainty and misalignment. You need it when weekly team alignment and backlog management become scattered.

To plan weekly work across dev, clients, marketing, lab, and framework directions, trigger the ritual on Monday or via explicit commands. It enforces phase-by-phase execution, reads backlog and plan files, and aligns strategy with tactics across all domains.

The best way to close a prior week and generate progress and plans is following a seven-phase guided execution cycle. It enforces explicit approvals and guardrails, reading existing backlog and plan files to align strategy with tactics while summarizing outcomes.

Weekly planning requires reading existing backlog and plan files to orchestrate cross-domain work. The guided execution enforces phase-by-phase processing with explicit approvals, relying on these files to align strategy with tactics across framework, lab, dev, clients, and marketing directions.

Yes, you can trigger the weekly planning cycle manually through explicit commands instead of waiting for the automated Monday trigger. The ritual begins Phase 1 and follows the seven phases in order, enforcing phase-by-phase execution with explicit approvals.

Guided phase-by-phase execution matters because it enforces explicit approvals and guardrails that maintain strategic focus. By structuring the weekly cycle to clean backlogs and analyze performance, it reduces uncertainty and misalignment while aligning strategy with tactics.