/simple-gemini

name: simple-gemini
description: Collaborative documentation and test code writing workflow using zen mcp's clink to launch gemini CLI session in WSL (via 'gemini' command) where all writing operations are executed. Use this skill when the user requests "use gemini to write test files", "use gemini to write documentation", "generate related test files", "generate an explanatory document", or similar document/test writing tasks. The gemini CLI session acts as the specialist writer, working with the main Claude model for context gathering, outline approval, and final review. For test code, codex CLI (also launched via clink) validates quality after gemini completes writing.

Gemini Documentation & Test Writer

Overview

This skill provides a collaborative writing workflow where gemini CLI (launched via zen mcp's clink tool as a WSL command `gemini`) serves as a specialist writer for markdown documentation and test code. All writing operations are executed within the gemini CLI session environment, while the main Claude model handles context gathering, user interaction, and test execution. For test code, codex CLI (also launched via clink as WSL command `codex`) performs quality validation after gemini completes the initial writing.

**Technical Architecture:**

• **zen-mcp clink**: Acts as the bridge to launch CLI tools in WSL environment
• **gemini CLI session**: Opened via `gemini` command in WSL, where all document/test writing happens
• **codex CLI session**: Opened via `codex` command in WSL for code review tasks
• **Conversation context**: Maintained via `continuation_id` across CLI sessions

**Division of Responsibilities:**

• **Gemini CLI Session** (in WSL): Specialist writer for .md documents and test code, all writing executed inside this CLI environment
• **Main Claude Model**: Context gathering, CLI invocation orchestration, outline approval, test execution, final review
• **Codex CLI Session** (in WSL): Test code quality validation and correction, review executed inside this CLI environment
• **User**: Approval of outlines and final review (in Interactive Mode) or information recipient (in Automated Mode)

When to Use This Skill

Trigger this skill when the user or main model requests:

• "Use gemini to write test files"
• "Use gemini to write documentation"
• "Generate related test files"
• "Generate an explanatory document"
• Commands from Claude or codex to write documentation
• Any request to create .md documentation or test code files

Operation Mode (automation_mode - READ FROM SSOT)

automation_mode definition and constraints: See CLAUDE.md「📚 共享概念速查」

**This skill's role**: Skill Layer (read-only), read from context `[AUTOMATION_MODE: true/false]`

• `false` → Interactive: Requires user confirmation (outline, review, test corrections)
• `true` → Automated: Autonomous decisions, escalate only for critical issues, record to auto_log.md

Coverage Target Management (READ ONLY - G9 Compliance)

coverage_target definition and constraints: See CLAUDE.md「📚 共享概念速查」

**This skill's role**: Skill Layer (read-only), read from context `[COVERAGE_TARGET: X%]`, use when generating/evaluating test code (default 85% if missing)

Workflow Decision Tree

User Request
    │
    ├─→ Document Writing? ──→ Document Writing Workflow
    │
    └─→ Test Code Writing? ──→ Test Code Writing Workflow

Document Writing Workflow

Phase 1: Preparation & Context Gathering (Main Claude)

**Main Claude's Responsibility:**

1. **Understand the Documentation Need:**

• What type of document? (README, PROJECTWIKI, ADR, CHANGELOG, technical spec, etc.)
• What is the purpose and audience?
• What scope should be covered?

2. **Gather Context:**

• Read relevant code files if needed
• Check existing documentation structure
• Identify project standards from CLAUDE.md
• **Context File Selection:**
• **Interactive Mode (automation_mode = false)**: Ask user: "Do you need me to reference existing code/files for this document?"
• **Automated Mode (automation_mode = true)**: Auto-analyze project structure and select relevant files, log decision to auto_log.md

3. **Identify Document Requirements:**

• For CLAUDE.md mandated documents (PROJECTWIKI.md, CHANGELOG.md, ADRs):
• Apply standards from `references/doc_templates/README.md` (on-demand template loading)
• Follow CLAUDE.md Project Knowledge Base Content Structure and Generation Rules Unified Template
• For other documents:
• Determine appropriate structure
• Identify key sections needed

Phase 2: Outline Generation (Gemini CLI Session)

**Invoke Gemini CLI Session via `mcp__zen__clink`:**

Tool: mcp__zen__clink
Parameters:
- cli_name: "gemini"  # Launches 'gemini' command in WSL
- prompt: "Generate a detailed outline for [document type] covering [scope].
          Context: [provide all gathered context]
          Requirements: [standards from CLAUDE.md if applicable]
          Purpose: [document purpose]
          Audience: [target readers]"
- files: [list of relevant file paths for context - absolute paths]
- role: "default" (or "planner" for complex planning tasks)
- continuation_id: [if continuing from previous gemini CLI session]

**What Happens:** 1. zen-mcp clink opens a gemini CLI session in WSL 2. The prompt and files are passed into the gemini CLI environment 3. All outline generation work is executed inside the gemini CLI session 4. The gemini CLI session returns the completed outline 5. The session context is preserved via continuation_id for future calls

**Gemini CLI Session Output:** Detailed outline with:

• Main sections and subsections
• Key points to cover in each section
• Special considerations (diagrams, code examples, etc.)

Phase 3: Outline Review & Approval (Main Claude + User)

**Main Claude's Responsibility:**

** automation_mode check**: `[AUTOMATION_MODE: false]` → Interactive / `true` → Automated

Interactive Mode (automati