phase-context-gathering

To gather complete context for a planning phase, you need a roadmap and SPEC/PLAN inputs to scan target directories, identify gray areas, and produce a structured CONTEXT.md with actionable insights and dependency inventories.

Gray areas in a codebase are underspecified regions, missing interfaces, and ambiguous module connections. You detect them by adaptively scanning the codebase to surface unresolved questions and document their severities for architectural review.

Yes, you need a roadmap and SPEC/PLAN inputs to define the scope before inventorying dependencies and APIs. These inputs align stakeholders and ensure the scanner targets the correct directories for context scoping.

You onboard a builder by running a context gathering step over the codebase to generate a CONTEXT.md. This document provides a single source of truth containing structured inventories of relevant files, APIs, and conventions.

The best way to document underspecified regions before phase execution is to scan the codebase for gray areas and capture open questions. This produces a CONTEXT.md that unblocks builders by guiding execution with actionable insights.

Underspecified phase context causes rework and delays because builders encounter missing interfaces and ambiguous module connections during execution. Adaptive context gathering surfaces these gray areas early to unblock builders and prevent architectural errors.