gromit-decompose

Read .gromit/plans markdown files and output JSON bead definitions.

3|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/danabrams/gromit --skill gromit-decompose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gromit-decompose
Source: https://github.com/danabrams/gromit/tree/main/skills/gromit-decompose
Command: npx skills add https://github.com/danabrams/gromit --skill gromit-decompose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes implementation plans into bead definitions for automated creation via bd create, enabling a deterministic, machine-readable workflow from plan to beads.

Core Features & Use Cases

  • Reads .gromit/plans/<name>.md and extracts the plan frontmatter and the Implementation Tasks section
  • Maps each task to 1-3 beads following strict sizing rules to ensure atomic, testable work items
  • Outputs a JSON array of bead definitions suitable for automated bead creation without human narration

Quick Start

Run gromit decompose on a plan to generate a machine-readable JSON bead array.

Frequently Asked Questions about gromit-decompose

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

FAQPage Schema
How do I convert a markdown plan into JSON bead definitions?

To convert a markdown plan into JSON bead definitions, use the gromit decompose tool to read the .gromit/plans/<name>.md file. It extracts the plan frontmatter and Implementation Tasks section, outputting a JSON array of bead definitions.

What is the bead sizing limit when decomposing implementation tasks?

The bead sizing limit when decomposing implementation tasks is a strict 1-3 beads per task. This strict sizing rule ensures that each resulting bead definition represents atomic, testable work items.

Can I automate bead creation from plan files without interactive prompts?

Yes, you can automate bead creation from plan files without interactive prompts. The gromit decompose tool is designed for non-interactive use, reading plan files and producing only machine-readable JSON output for automated workflows.

What do I need to generate bead definitions from a plan?

To generate bead definitions from a plan, you need a markdown plan file located at .gromit/plans/<name>.md. The file must contain the plan frontmatter and an Implementation Tasks section for the tool to parse.

Why are my decomposed beads not self-contained for automated creation?

If your decomposed beads are not self-contained, ensure your plan file's Implementation Tasks section is properly structured. The tool applies strict 1-3 bead sizing rules per task to ensure beads are self-contained for automated creation via bd create.