Gepetto

作者 softaworks3027f20f3181無授權條款2.5K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫7 個月前更新

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

僅含說明Productivity & WorkflowAI & Agents
AI 產生的概覽

將 Markdown 規格文件轉化為經研究、審查並分節的實作計畫與執行檔案。

功能
Gepetto 統籌多步驟規劃流程：研究、利害關係人訪談、規格綜整、計畫產生、外部多模型審查，以及將計畫拆分為自成一體的分節檔案。它會將一系列 Markdown 產物寫入規劃目錄，包括研究結果、訪談紀錄、綜整規格、實作計畫、整合說明、審查輸出與分節檔案。它也會產生用於自主實作的執行檔案，例如 ralph-loop 提示詞與 Ralphy PRD。
適用情境
適用於需要充分實作前分析的功能規劃，包括研究與利害關係人輸入。適合已有規格文件、希望在實作前取得由外部模型審查的詳細分節計畫的情境。
執行需求
呼叫時需提供 Markdown 規格檔案路徑（以 .md 結尾），規劃目錄由其父目錄推斷。它使用子代理、網路搜尋，並透過 Bash 呼叫外部工具（Gemini 與 Codex）進行審查，同時寫入大量 Markdown 檔案。它不附帶指令碼，僅為指示。

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═══════════════════════════════════════════════════════════════
This skill requires a markdown spec file path (must end with .md).The planning directory is inferred from the spec file's parent directory.
To start a NEW plan:  1. Create a markdown spec file describing what you want to build  2. It can be as detailed or as vague as you like  3. Place it in a directory where gepetto can save planning files  4. Run: /gepetto @path/to/your-spec.md
To RESUME an existing plan:  1. Run: /gepetto @path/to/your-spec.md
Example: /gepetto @planning/my-feature-spec.md═══════════════════════════════════════════════════════════════

Do not continue. Wait for user to re-invoke with a .md file path.

3. Setup Planning Session

Determine session state by checking existing files:

  1. Set planning_dir = parent directory of the spec file

  2. Set initial_file = the spec file path

  3. Scan for existing planning files:

    • claude-research.md
    • claude-interview.md
    • claude-spec.md
    • claude-plan.md
    • claude-integration-notes.md
    • claude-ralph-loop-prompt.md
    • claude-ralphy-prd.md
    • reviews/ directory
    • sections/ directory

  4. Determine mode and resume point:

Files FoundModeResume From
NonenewStep 4
research onlyresumeStep 6 (interview)
research + interviewresumeStep 8 (spec synthesis)
+ specresumeStep 9 (plan)
+ planresumeStep 10 (external review)
+ reviewsresumeStep 11 (integrate)
+ integration-notesresumeStep 12 (user review)
+ sections/index.mdresumeStep 14 (write sections)
all sections completeresumeStep 15 (execution files)
+ claude-ralph-loop-prompt.md + claude-ralphy-prd.mdcompleteDone
  1. Create TODO list with TodoWrite based on current state

Print status:

Planning directory: {planning_dir}Mode: {mode}

If resuming:

Resuming from step {N}To start fresh, delete the planning directory files.

Logging Format

═══════════════════════════════════════════════════════════════STEP {N}/17: {STEP_NAME}═══════════════════════════════════════════════════════════════{details}Step {N} complete: {summary}───────────────────────────────────────────────────────────────

Workflow

4. Research Decision

See research-protocol.md [blocked].

  1. Read the spec file
  2. Extract potential research topics (technologies, patterns, integrations)
  3. Ask user about codebase research needs
  4. Ask user about web research needs (present derived topics as multi-select)
  5. Record which research types to perform in step 5

5. Execute Research

See research-protocol.md [blocked].

Based on decisions from step 4, launch research subagents:

  • Codebase research: Task(subagent_type=Explore)
  • 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 [blocked]

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 [blocked]

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.

Step 1: Write <planning_dir>/claude-integration-notes.md documenting:

  • What suggestions you're integrating and why
  • What suggestions you're NOT integrating and why

Step 2: Update <planning_dir>/claude-plan.md with the integrated changes.

12. User Review of Integrated Plan

Use AskUserQuestion:

The plan has been updated with external feedback. You can now review and edit claude-plan.md.
If you want Claude's help editing the plan, open a separate Claude session - this sessionis mid-workflow and can't assist with edits until the workflow completes.
When you're done reviewing, select "Done" to continue.

Options: "Done reviewing"

Wait for user confirmation before proceeding.

13. Create Section Index

See section-index.md [blocked]

Read claude-plan.md. Identify natural section boundaries and create <planning_dir>/sections/index.md.

CRITICAL: index.md MUST start with a SECTION_MANIFEST block. See the reference for format requirements.

Write index.md before proceeding to section file creation.

14. Write Section Files — Parallel Subagents

See section-splitting.md [blocked]

Launch parallel subagents - one Task per section for maximum efficiency:

  1. First, parse sections/index.md to get the SECTION_MANIFEST list
  2. Then launch ALL section Tasks in a single message (parallel execution):
# Launch all in ONE message for parallel execution:
Task(  subagent_type="general-purpose",  prompt="""  Write section file: section-01-{name}
  Inputs:  - <planning_dir>/claude-plan.md  - <planning_dir>/sections/index.md
  Output: <planning_dir>/sections/section-01-{name}.md
  The section file must be COMPLETELY SELF-CONTAINED. Include:  - Background (why this section exists)  - Requirements (what must be true when complete)  - Dependencies (requires/blocks)  - Implementation details (from the plan)  - Acceptance criteria (checkboxes)  - Files to create/modify
  The implementer should NOT need to reference any other document.  """)
Task(  subagent_type="general-purpose",  prompt="Write section file: section-02-{name} ...")
Task(  subagent_type="general-purpose",  prompt="Write section file: section-03-{name} ...")
# ... one Task per section in the manifest

Wait for ALL subagents to complete before proceeding.

15. Generate Execution Files — Subagent

Delegate to subagent to reduce main context token usage:

Task(  subagent_type="general-purpose",  prompt="""  Generate two execution files for autonomous implementation.
  Input files:  - <planning_dir>/sections/index.md (has SECTION_MANIFEST)  - <planning_dir>/sections/section-*.md (all section files)
  OUTPUT 1: <planning_dir>/claude-ralph-loop-prompt.md  For ralph-loop plugin. EMBED all section content inline.
  Structure:  - Mission statement  - Full content of sections/index.md  - Full content of EACH section file (embedded, not referenced)  - Execution rules (dependency order, verify acceptance criteria)  - Completion signal: <promise>ALL-SECTIONS-COMPLETE</promise>
  OUTPUT 2: <planning_dir>/claude-ralphy-prd.md  For Ralphy CLI. REFERENCE section files (don't embed).
  Structure:  - PRD header  - How to use (ralphy --prd command)  - Context explanation  - Checkbox task list: one "- [ ] Section NN: {name}" per section
  Write both files.  """)

Wait for subagent completion before proceeding.

16. Final Status

Verify all files were created successfully:

  • All section files from SECTION_MANIFEST
  • claude-ralph-loop-prompt.md
  • claude-ralphy-prd.md

17. Output Summary

Print generated files and next steps:

═══════════════════════════════════════════════════════════════GEPETTO: Planning Complete═══════════════════════════════════════════════════════════════
Generated files:  - claude-research.md (research findings)  - claude-interview.md (Q&A transcript)  - claude-spec.md (synthesized specification)  - claude-plan.md (implementation plan)  - claude-integration-notes.md (feedback decisions)  - reviews/ (external LLM feedback)  - sections/ (implementation units)  - claude-ralph-loop-prompt.md (for ralph-loop plugin)  - claude-ralphy-prd.md (for Ralphy CLI)
How to implement:
Option A - Manual (recommended for learning/control):  1. Read sections/index.md to understand dependencies  2. Implement each section file in order  3. Each section is self-contained with acceptance criteria
Option B - Autonomous with ralph-loop (Claude Code plugin):  /ralph-loop @<planning_dir>/claude-ralph-loop-prompt.md --completion-promise "COMPLETE" --max-iterations 100
Option C - Autonomous with Ralphy (external CLI):  ralphy --prd <planning_dir>/claude-ralphy-prd.md  # Or: cp <planning_dir>/claude-ralphy-prd.md ./PRD.md && ralphy═══════════════════════════════════════════════════════════════

來源與署名

來源：softaworks/agent-toolkit位於skills/gepetto提交3027f20

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 softaworks/agent-toolkit 的技能

C4 Architecture

softaworks

使用 Mermaid 圖表產生 C4 模型架構文件。

Software Development2.5K7 個月前更新

Writing Clearly And Concisely

softaworks

套用 Strunk《風格的要素》規則與 AI 寫作模式清單，讓給人閱讀的文字更清晰、更精簡。

Writing & Content2.5K7 個月前更新

Web To Markdown

softaworks

使用本機安裝的 web2md 命令列工具（Puppeteer 與 Readability）將網頁 URL 轉換為乾淨的 Markdown。

Productivity & Workflow2.5K7 個月前更新

Skill Judge

softaworks

依據官方規範與最佳實務評估 Agent Skill 的設計品質，提供多維度評分與改進建議。

AI & Agents2.5K7 個月前更新

Ship Learn Next

softaworks

把課程、文章等學習內容轉換成 Ship-Learn-Next 行動計畫，包含可交付的每週迭代。

Learning & Education2.5K7 個月前更新

Reducing Entropy

softaworks

引導代理以刪除為優先，透過衡量最終程式碼量來最小化程式碼庫總規模。

Software Development2.5K7 個月前更新

更多Productivity & Workflow技能

Notion Spec To Implementation

openai

精選

把 Notion 規格轉換為實作計畫、關聯任務與進度更新。

Productivity & Workflow27K4 週前更新

Notion Research Documentation

openai

精選

檢索 Notion 頁面並將發現綜整為附引用的簡報、比較或報告，再發佈回 Notion。

Productivity & Workflow27K4 週前更新

Notion Meeting Intelligence

openai

精選

運用 Notion 脈絡與研究準備會議議程和會前讀物，並依與會者和會議類型調整內容。

Productivity & Workflow27K4 週前更新

Linear

openai

精選

引導代理透過 Linear MCP 伺服器管理 Linear 中的問題、專案、週期與團隊工作流程。

Productivity & Workflow27K4 週前更新

Define Goal

openai

精選

把模糊意圖轉化為具體、可衡量且帶有驗證證據與範圍界線的目標。

Productivity & Workflow27K4 週前更新

Smb Onboard

anthropics

精選

引導小型企業主完成首次設定：連接工具、執行一次展現價值的配方、記錄業務背景並設定每週檢查節奏。

Productivity & Workflow27K今天更新