se-challenge-plan

Surface hidden assumptions in an implementation plan by applying focused questioning and context inspection to challenge sequencing, risks, and decisions. This review process exposes misalignments and gaps before development work begins.

Plan risk analysis is the process of stress-testing a proposed approach against project context and existing decisions. It identifies hidden assumptions, validates sequencing, and captures potential misalignments before code implementation starts.

Review project context for plan feasibility by guiding focused questioning against domain language, existing decisions, and test strategy. This surfaces gaps and validates alignment before starting work on a new module.

Use decision records in plan design when stress-testing a proposed approach to capture context-aware reviews. They document focused questioning outcomes, ensuring hidden assumptions and risks are formally recorded before implementation.

Yes, you can challenge plan sequencing and test strategy by running focused questioning against project context. This stress-tests the proposed approach to surface hidden risks and assumptions before development starts.

Stress-testing a proposed approach is limited by the availability of project context, domain language, and existing decisions. It relies on focused questioning to surface gaps, meaning incomplete documentation reduces the accuracy of risk analysis.