pre-phase-briefing

What problem does it solve?

Starting a new project phase without reviewing past lessons or validating codebase assumptions leads to repeated mistakes, wasted work, and plans that do not align with actual existing code.

Core Features & Use Cases

• Retrospective Review: Automatically pulls and internalizes lessons learned and persistent user directives from prior phase retrospectives or historical project bundles to avoid repeating past errors across phases and projects.
• Codebase Reality Checks: Runs asynchronous, fanned-out validation of all code, module, and configuration references in a plan to confirm existence, current state, and alignment with assumptions before any work begins.
• Use Case: For a multi-phase software refactor, use this skill to carry forward lessons from prior failed test runs and catch incorrect assumptions about existing service configurations before writing the new phase plan.

Quick Start

Use the pre-phase-briefing skill to review the previous phase's retrospective and verify all code references in your new phase plan before starting any work.