gemini-plan-detailed

Generates bounded implementation plans for single bug fixes, features, or refactors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a loosely described bug fix, small feature, or targeted refactor into a concrete, immediately implementable plan with enumerated file changes, verification commands, and testable acceptance criteria, so a single developer or one Gemini thread can execute the work end to end without open decisions. ## Core Features & Use Cases - Bounded change planning: Researches the repo with local reads (rg, git status, targeted file inspection) and produces a plan listing every file, entity, action, and reason, capped at roughly 8 source files or 3 distinct changes. - Verification contract: Every plan includes machine-checkable verification commands and acceptance criteria, with support for referencing roadmap goal IDs like EC-<ALIAS>-<N> instead of restating them. - Handoff and manifest integration: Writes a structured handoff artifact, updates plans/manifest.json via the phase_loop_runtime plan_manifest helper, and records a per-run reflection for continuous skill improvement. - Use Case: A developer asks for a plan to fix a pagination bug in an API endpoint; the skill inspects the relevant files, then returns a plan artifact with the exact changes, docs impact, ordered steps, and the test commands that prove the fix. ## Quick Start Ask the agent to create a detailed implementation plan for your specific bug fix or small feature, for example: plan the change to add rate limiting to the login endpoint.

Frequently Asked Questions about gemini-plan-detailed

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

FAQPage Schema
How do I create a detailed implementation plan for a bug fix?▼

Describe the bug or small feature and invoke the planning skill; it researches the repo with git status, recent log, and targeted rg searches, then returns a plan listing every file change, verification commands, and acceptance criteria. It does not run tests or begin implementation during planning.

When should I use a detailed plan instead of a phase roadmap?▼

Use a detailed plan when one developer or one Gemini thread should do the work end to end for a single bounded change. The phase roadmap pipeline is for multi-phase initiatives; this skill explicitly recommends splitting plans that exceed about 8 source files or 3 distinct changes.

Does the planning skill run tests or modify code?▼

No. In planning-only runs it does not execute tests, builds, formatters, or other verification commands, and it does not begin implementation. It lists the commands in the plan and runs verification only when the user explicitly asks for validation or execution.

Can the plan reference existing roadmap acceptance criteria?▼

Yes. If the bounded change implements a roadmap phase goal, the plan references its EC-<ALIAS>-<N> identifier with the proving command instead of restating the criterion. Standalone changes with no roadmap goal use plain testable assertions.

What artifacts does the planning workflow produce?▼

It writes a plan markdown artifact under plans/, a handoff file under .dev-skills/handoffs/gemini-plan-detailed/ with a latest.md pointer, a best-effort entry in plans/manifest.json, and a reflection file for every non-trivial run.