Development Execution Planning Specification

Perceive

1. Context Gathering: Systematically map the codebase using search tools (grep_search, glob) to understand file structures and existing patterns.
2. Constraint Check: Identify coding styles, configuration files (e.g., package.json, gemini-extension.json), and framework dependencies.
3. Mandatory Deep Dive: Validate all assumptions by reading relevant file contents. Do not skip this step.

Reason

1. Gap Analysis: Clearly define the delta between the current codebase state and the user's desired state.
2. Architectural Fit: Ensure the proposed solution aligns with the established architecture (e.g., separating logic into skills/, using commands/ for entry points).
3. Risk Assessment: Identify potential breaking changes, ambiguous requirements, or side effects.
4. Dependency Chain: Determine the strictly logical order of operations (e.g., "Create directory before creating file").