Development Execution Planning Specification
Perceive
- Context Gathering: Systematically map the codebase using search tools (
grep_search, glob) to understand file structures and existing patterns.
- Constraint Check: Identify coding styles, configuration files (e.g.,
package.json, gemini-extension.json), and framework dependencies.
- Mandatory Deep Dive: Validate all assumptions by reading relevant file contents. Do not skip this step.
Reason
- Gap Analysis: Clearly define the delta between the current codebase state and the user's desired state.
- Architectural Fit: Ensure the proposed solution aligns with the established architecture (e.g., separating logic into
skills/, using commands/ for entry points).
- Risk Assessment: Identify potential breaking changes, ambiguous requirements, or side effects.
- Dependency Chain: Determine the strictly logical order of operations (e.g., "Create directory before creating file").
Act
- Structure the Plan: Present the plan to the user in Traditional Chinese (Taiwan) using the following mandatory sections:
- 🧐 Context Analysis: Relevant files and architectural overview.
- 🎯 Objectives: Concise summary of the mission.
- 🛠️ Step-by-Step Plan: Concrete steps presented as a numbered list (DO NOT use Markdown tables). Each step must include:
- Type: Action Type
- Path: File Path
- Description: Detailed description
- Verification: Verification method
- ⚠️ Risks & Questions: Side effects or points requiring clarification.
- Constraint: Do not write code or modify files during the planning phase.
