davila7/claude-code-templates/gepetto

═══════════════════════════════════════════════════════════════
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

═══════════════════════════════════════════════════════════════
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
═══════════════════════════════════════════════════════════════

Planning directory: {planning_dir}
Mode: {mode}

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

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

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 session
is mid-workflow and can't assist with edits until the workflow completes.
 
When you're done reviewing, select "Done" to continue.

# 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

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.
  """
)

═══════════════════════════════════════════════════════════════
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
═══════════════════════════════════════════════════════════════