implement-mode

name	implement-mode
description	Executes approved roadmaps or requests with a verification-first mindset and robust troubleshooting. Use when you need to implement specific changes and provide a detailed session summary.

Implement-Mode

GOAL: Execute approved project modifications safely and efficiently following standard implementation protocols.

WHEN: Invoke this skill when the user explicitly requests the execution of an approved roadmap or request.

NOTE: This skill requires explicit user authorization for high-risk operations and always restores read-only mode upon completion.

Efficiency directives

• Optimize all operations for agent, token, and context efficiency
• Optimize for minimal output
• Batch operations on file groups, avoid individual file processing
• Use parallel execution when possible
• Target only relevant files
• Reduce token usage

Task management

• Use the native write_todos tool for all task management.
• Break down complex work into cohesive subtasks.
• Maintain accurate task statuses (pending, in_progress, completed) to provide visibility via the CLI progress indicator.

Workflow

Step 1: Activate write access

• Invoke the write-mode skill.
• Capture status (SUCCESS, WARN, ERROR).
• Handle status:
  • ERROR: Halt and report.
  • SUCCESS/WARN: Continue.

Step 2: Initialize

• Initialize the task list using write_todos.
• State the goal, risk level, and management method.

Step 3: Execute roadmap

• Apply the 6-step reasoning engine:
  1. Analyze: Prerequisites and order of operations.
  2. Evaluate: Consequences and risks.
  3. Identify: Likely causes and edge cases.
  4. Revise: Roadmaps based on observations.
  5. Incorporate: All tools, policies, and constraints.
  6. Retry: Transient errors.
• Follow the risk-adaptive workflow (TRIVIAL, LOW, MEDIUM, HIGH).
• Perform modifications.

Step 4: Verify & fix

• Run tests, linters, and builds.
• On failure:
  1. Diagnose: Analyze the error to identify the root cause.
  2. Fix: Attempt to resolve the issue autonomously.
  3. Retry: Verify the fix.
• Escalation: If the issue persists after reasonable attempts, halt and report.

Step 5: Restore safety

• Invoke the readonly-mode skill.

Step 6: Report

• Provide the session summary.
• DONE

Session summary format

Overview:

• Objective: [Goal]
• Risk: [Level]
• Duration: [Time]

Tasks:

• ✅ [Task] - [Result]
• 🔄 [Task] - [Status]
• 📋 [Task] - [Pending]

Verification:

• Tests: [Pass/Fail]
• Quality: [Lint/Build Status]
• Coverage: [Status]

Notes:

• [Key decisions/blockers]

Output

Files created/modified:

• Project files modified during execution.
• .gemini_readonly - Restored at the end.

Status communication: Report the detailed session summary.