keystone:orient

Code planning involves loading the current codebase state, matching regional idioms, and referencing process guides to generate a written plan. This plan establishes consensus between the agent and user before any implementation begins.

Codebase analysis for implementation preparation is done by loading the current codebase state and matching idioms specific to the touched region. Referencing relevant process guides ensures best practices are followed during the planning phase.

Yes, code planning requires access to both charter and corpus directories. These directories provide the necessary context and state information needed to execute the orient action and generate an accurate written implementation plan.

Project planning incorporates idioms specific to the touched region of the codebase to ensure context-aware preparation. This allows the generated written plan to respect existing patterns and best practices before implementation starts.

Yes, code planning references relevant process guides to ensure best practices are followed. These guides are loaded alongside the codebase state and matching idioms to produce a comprehensive written plan for consensus before implementation.

Generating a written plan before implementation ensures both the agent and user agree on the approach. This prevents misalignment by establishing a clear, structured plan based on the current codebase state, idioms, and process guides.