plan-contextualize

A plan_context.md file eliminates repeated codebase exploration by packing repository exploration output into a single, consumable context file. Generated after plan approval, it provides the executor model with a complete, offline copy of relevant codebase rules and context.

To generate a deterministic plan_context.md, trigger the contextualization process after plan approval. It consumes prerequisites from the machine current-task plan.md file and writes the complete repository exploration pack directly to disk as a fixed artifact.

Yes, an approved plan.md file is required before creating a repository exploration pack. The process executes strictly after plan approval to ensure a validated exploration surface, consuming the approved status and defined prerequisites from the machine current-task directory.

Yes, generating a context pack keeps doctrine files separate from the exploration output. The plan_context.md file is produced as the primary artifact, while doctrine files remain untouched on disk for the build execution phase to read directly.

A limitation of packing repository exploration into a single context file is its dependency on an approved plan.md and related limits.md files. Without this validated prerequisite state, it cannot generate the deterministic plan_context.md artifact for the build phase.