Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/gepetto
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
📊 Stats
Stars29,852
Forks3,189
LanguagePython
LicenseMIT
📦 Ships with claude-code-templates
</> SKILL.md
gepetto.SKILL.md
---name: gepetto
description: Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
---# Gepetto
Orchestrates a multi-step planning process: Research → Interview → Spec Synthesis → Plan → External Review → Sections
## CRITICAL: First Actions
**BEFORE anything else**, do these in order:
### 1. Print Intro
Print intro banner immediately:
```
═══════════════════════════════════════════════════════════════
GEPETTO: AI-Assisted Implementation Planning
═══════════════════════════════════════════════════════════════
Research → Interview → Spec Synthesis → Plan → External Review → Sections
Note: GEPETTO will write many .md files to the planning directory you pass it
```
### 2. Validate Spec File Input
**Check if user provided @file at invocation AND it's a spec file (ends with `.md`).**
If NO @file was provided OR the path doesn't end with `.md`, output this and STOP:
```
═══════════════════════════════════════════════════════════════
GEPETTO: Spec File Required
═══════════════════════════════════════════════════════════════
- **Web research:** `Task(subagent_type=Explore)` with WebSearch
If both are needed, launch both Task tools in parallel (single message with multiple tool calls).
**Important:** Subagents return their findings - they do NOT write files directly. After collecting results from all subagents, combine them and write to `<planning_dir>/claude-research.md`.
Skip this step entirely if user chose no research in step 4.
### 6. Detailed Interview
See [interview-protocol.md](references/interview-protocol.md)
Run in main context (AskUserQuestion requires it). The interview should be informed by:
- The initial spec
- Research findings (if any)
### 7. Save Interview Transcript
Write Q&A to `<planning_dir>/claude-interview.md`
### 8. Write Initial Spec (Spec Synthesis)
Combine into `<planning_dir>/claude-spec.md`:
- **Initial input** (the spec file)
- **Research findings** (if step 5 was done)
- **Interview answers** (from step 6)
This synthesizes the user's raw requirements into a complete specification.
### 9. Generate Implementation Plan
Create detailed plan → `<planning_dir>/claude-plan.md`
**IMPORTANT**: Write for an unfamiliar reader. The plan must be fully self-contained - an engineer or LLM with no prior context should understand *what* we're building, *why*, and *how* just from reading this document.
### 10. External Review
See [external-review.md](references/external-review.md)
Launch TWO subagents in parallel to review the plan:
1. **Gemini** via Bash
2. **Codex** via Bash
Both receive the plan content and return their analysis. Write results to `<planning_dir>/reviews/`.
### 11. Integrate External Feedback
Analyze the suggestions in `<planning_dir>/reviews/`.
You are the authority on what to integrate or not. It's OK if you decide to not integrate anything.
