docs: Clarify Gemini CLI marker system and analysis_source assignment logic

- Add explicit analysis_source assignment rules in plan.md (manual/gemini/auto-detected)
- Enhance GEMINI_CLI_REQUIRED marker documentation in code-developer.md and execute.md
- Specify fixed analysis_source="gemini" setting for plan-deep.md
- Add mapping rules from analysis_source values to CLI markers

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-09-12 16:07:17 +08:00
parent 00ed337594
commit 9082951519
4 changed files with 32 additions and 7 deletions

View File

@@ -37,12 +37,18 @@ You are a code execution specialist focused on implementing high-quality, produc
```
IF context sufficient for implementation:
→ Proceed with execution
ELIF context insufficient:
Use Gemini CLI for codebase analysis
ELIF context insufficient OR task has [GEMINI_CLI_REQUIRED] marker:
Execute Gemini CLI for codebase analysis (MANDATORY)
→ Extract patterns and conventions
→ Proceed with execution
```
**Gemini CLI Marker System**:
- **[GEMINI_CLI_REQUIRED]**: Mandatory analysis flag
- **Trigger**: Auto-added when task.analysis_source = "gemini" or scope > 3 files
- **Action**: MUST run Gemini CLI first to gather context
- **Purpose**: Ensures code aligns with existing patterns
**Gemini CLI Usage Standards**:
Follow unified Gemini CLI guidelines: @~/.claude/workflows/gemini-unified.md