gemini-execute-detailed

Executes one detailed implementation plan with verification, acceptance checks, and PR publication.

2|1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Consiliency/agent-harness --skill gemini-execute-detailed-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gemini-execute-detailed
Source: https://github.com/Consiliency/agent-harness/tree/main/skills-src/gemini/gemini-execute-detailed
Command: npx skills add https://github.com/Consiliency/agent-harness --skill gemini-execute-detailed-consiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing a bounded plan by hand risks unscoped edits, unverified changes, and unsafe git operations like committing to main or a shared branch. This Skill executes one detailed plan artifact end to end inside a Gemini thread, enforcing plan scoping, verification, acceptance checks, and safe publication. ## Core Features & Use Cases - Bounded plan execution: Reads a detailed plan artifact from gemini-plan-detailed, validates its Changes, Verification, and Acceptance criteria sections, and applies only the declared edits. - Git safety and publication: Establishes a safe worktree off a fresh base ref, never commits to main or unowned branches, and publishes a draft or ready PR via the phase_loop_runtime publishing primitive. - Verification and reflection closeout: Runs every verification command, checks acceptance criteria, classifies dirty paths, updates the plan manifest lifecycle, and writes a mandatory run reflection. - Use Case: After gemini-plan-detailed produces a plan for a bug fix, invoke this Skill to implement the changes in an isolated worktree, run the test suite, and open a draft PR without touching the main branch. ## Quick Start Execute the latest detailed plan from gemini-plan-detailed, verify it, and open a pull request from a safe branch.

Frequently Asked Questions about gemini-execute-detailed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a detailed implementation plan with Gemini?▼

Provide the detailed plan artifact path, or let the Skill resolve the latest valid handoff from gemini-plan-detailed. It validates the Changes, Verification, and Acceptance criteria sections, applies edits in a safe worktree, runs verification, and publishes a PR.

How does the executor avoid committing to main or a shared branch?▼

Before editing, it resolves a fresh base ref and creates a dedicated worktree and branch whenever the current checkout is main, protected, shared, or dirty. All edits, verification, and commits happen in that tree, and force-push or merges are never used.

When does it open a draft PR versus a ready PR?▼

It opens a draft PR when dependencies remain or verification was partial or skipped, and a ready PR only when verification is complete. Publication runs through the phase_loop_runtime publish_from_worktree primitive with preflight checks for remote, auth, and branch safety.

What happens when verification fails during plan execution?▼

The run reports verification failed after one local diagnosis and repair attempt, marks the plan manifest lifecycle as failed, and records the failure in the mandatory reflection. Verified work is preserved on the safe branch and no ready PR is opened.

Can it run when a phase-loop runner owns the closeout?▼

Yes. When a runner or pipeline owns closeout, the Skill defers commit and publication entirely to the runner and skips worktree publication. It still requires the runner-owned verification artifact before reporting a successful closeout.