All skills
softaworks avatar

/gepetto

@1c0662a
by softaworkssoftaworks/agent-toolkit2.5k stars
230

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

Use this Skill: https://skilld.dev/gh/softaworks/agent-toolkit/gepetto

This session only. Nothing lands on disk.

referencessection-index.md

≈812 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Section Index Creation

Create <planning_dir>/sections/index.md to define implementation sections.

Input Files

  • <planning_dir>/claude-plan.md - implementation plan

Output

<planning_dir>/sections/
└── index.md

SECTION_MANIFEST Block

index.md MUST start with a SECTION_MANIFEST block:

<!-- SECTION_MANIFEST
section-01-foundation
section-02-config
section-03-parser
section-04-api
END_MANIFEST -->

# Implementation Sections Index

... rest of human-readable content ...

SECTION_MANIFEST Rules

  • Must be at the TOP of index.md (before any other content)
  • One section per line, format: section-NN-name (e.g., section-01-foundation)
  • Section numbers must be two digits with leading zero (01, 02, ... 12)
  • Section names use lowercase with hyphens (no spaces or underscores)
  • Numbers should be sequential (01, 02, 03...)
  • This block is parsed to track progress - the rest of index.md is for humans

Human-Readable Content

After the manifest block, include:

Dependency Graph

Table showing what blocks what:

| Section | Depends On | Blocks | Parallelizable |
|---------|------------|--------|----------------|
| section-01-foundation | - | section-02, section-03 | Yes |
| section-02-config | section-01 | section-04 | No |
| section-03-parser | section-01 | section-04 | Yes |
| section-04-api | section-02, section-03 | - | No |

Execution Order

Which sections can run in parallel:

1. section-01-foundation (no dependencies)
2. section-02-config, section-03-parser (parallel after section-01)
3. section-04-api (requires section-02 AND section-03)

Section Summaries

Brief description of each section:

### section-01-foundation
Initial project setup and configuration.

### section-02-config
Configuration loading and validation.

Guidelines

  • Natural boundaries: Split by component, layer, feature, or phase
  • Focused sections: One logical unit of work each
  • Parallelization: Consider which sections can run independently
  • Dependency direction: Earlier sections should not depend on later sections

Example index.md

<!-- SECTION_MANIFEST
section-01-foundation
section-02-core-libs
section-03-api-layer
section-04-frontend
section-05-integration
END_MANIFEST -->

# Implementation Sections Index

## Dependency Graph

| Section | Depends On | Blocks | Parallelizable |
|---------|------------|--------|----------------|
| section-01-foundation | - | all | Yes |
| section-02-core-libs | 01 | 03, 04 | No |
| section-03-api-layer | 02 | 05 | Yes |
| section-04-frontend | 02 | 05 | Yes |
| section-05-integration | 03, 04 | - | No |

## Execution Order

1. section-01-foundation (no dependencies)
2. section-02-core-libs (after 01)
3. section-03-api-layer, section-04-frontend (parallel after 02)
4. section-05-integration (final)

## Section Summaries

### section-01-foundation
Directory structure, config files, base setup.

### section-02-core-libs
Shared utilities and core libraries.

### section-03-api-layer
REST API endpoints and middleware.

### section-04-frontend
UI components and pages.

### section-05-integration
End-to-end integration and final wiring.

Source: SKILL.md on GitHub

3 warnings17d5 checks · Risk MEDIUM
  • Gen Agent Trust Hub17d

    The skill automates implementation planning by orchestrating research and multi-LLM reviews. However, it introduces security risks by invoking external CLI tools with flags that bypass manual approval and lacks sanitization for user-provided specification files that influence autonomous agent behavior.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    7/7 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 1c0662a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 8 months ago
  • planning
  • feature-development
  • requirements
  • specification
  • multi-agent
  • workflow
  • markdown
  • implementation

README badge

README badge for softaworks/agent-toolkit/gepetto

Orchestrates a multi-step planning workflow—research, stakeholder interview, spec synthesis, implementation plan, external LLM review, and sectionized breakdown—to produce detailed pre-implementation documentation and autonomous execution files. Targets feature planning that requires thorough analysis before coding begins.

Generated from the current SKILL.md.

Does this skill require a spec file to start?
Yes. Gepetto requires a markdown spec file path (ending in .md) passed at invocation. The skill will not proceed without it.
Can I resume a plan that was started earlier?
Yes. Gepetto scans the planning directory for existing files and resumes from the appropriate step, or starts fresh if no files exist.
What external models does this skill use for review?
Gepetto launches Gemini and Codex as parallel subagents in step 10 to review the implementation plan independently.
Does this skill write files to disk?
Yes. Gepetto writes markdown files to the planning directory inferred from your spec file's parent directory, including research, interviews, specs, plans, reviews, and section files.
Can I use the generated plan with other tools?
Yes. Gepetto outputs two execution files: claude-ralph-loop-prompt.md for the ralph-loop plugin and claude-ralphy-prd.md for the Ralphy CLI, both designed for autonomous implementation.

Generated from the current SKILL.md. These answers refresh after source changes.