expand

Decompose user tasks into atomic subtasks by analyzing the codebase.

19|3|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/GobbyAI/gobby --skill expand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expand
Source: https://github.com/GobbyAI/gobby/tree/main/src/gobby/install/shared/skills/expand
Command: npx skills add https://github.com/GobbyAI/gobby --skill expand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill decomposes a user-provided task into atomic subtasks by analyzing the codebase and surfacing the reasoning used, ensuring the expansion survives session compaction.

Core Features & Use Cases

  • Codebase analysis-driven decomposition: Breaks a task into small, testable units with dependencies.
  • Session-persistent expansions: Saves the expansion spec so it can resume after interruptions.
  • Plan-to-action workflow: Creates a structured task tree that Gobby can execute in phases.

Quick Start

Run /g expand #42 to decompose the task "Implement user authentication" into subtasks, and save the expansion spec before execution.

Frequently Asked Questions about expand

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

FAQPage Schema
How do I decompose a complex coding task into actionable subtasks?

Session-persistent expansions save your task decomposition spec so it can resume after interruptions. The expansion survives session compaction by relying on Gobby's internal task system to persist the plan.

Can I resume a task decomposition from a pending spec?

Yes, you can resume plan-based expansions from a pending spec. The skill persists the expansion spec for later phases, allowing you to pick up the multi-phase expansion workflow exactly where you left off.

What is the best way to break down a large software engineering plan into testable units?

The best way to break down a plan is using codebase analysis-driven decomposition. It surfaces visible reasoning to map your task into small, testable units and generates a structured task tree for execution.

Do I need a specific task system to use codebase analysis for task planning?

You can trigger codebase analysis by running the /g expand command with your task. For example, running /g expand with a task description will decompose it into subtasks and save the expansion spec before execution.

Why does my task expansion disappear after a session compaction?

Task expansions normally disappear because they are not persisted, but this skill saves an expansion spec specifically to survive session compaction. It relies on Gobby's internal task system to maintain the plan across interruptions.