pre-phase-briefing

Pre-phase checks are mandatory validation steps that review prior phase retrospectives and verify codebase references against their actual current state before planning begins. They prevent repeating past mistakes and planning work against incorrect codebase assumptions in multi-phase software development workflows.

You validate codebase assumptions by running asynchronous, fanned-out reality verification on all code, module, and configuration references in your plan. This confirms the existence and current state of referenced items, hard gating downstream planning work until all reference validations are complete.

Yes, retrospective review automatically pulls and internalizes lessons learned and persistent user directives from prior phase retrospectives or historical project bundles. This ensures past errors are not repeated across phases and projects in multi-phase software development workflows.

The best way is to perform codebase reality checks that run asynchronous, fanned-out validation of all configuration references in a plan. This confirms existence, current state, and alignment with assumptions before any work begins, hard gating downstream planning until validations are complete.

No, this phase planning workflow has zero external dependencies or components. It operates independently to assemble mandatory pre-phase context, fan out codebase reality verification, and hard gate downstream planning work until all reference validations are complete.

You should not use automated codebase reality verification for single-phase projects or workflows that do not require review of prior phase retrospectives. It is specifically designed for multi-phase software development workflows requiring validation of all referenced codebase items against their actual current state.