Get Stuff Done is the build tool I reach for when an idea is bigger than a single prompt. It’s a Claude Code plugin that walks a project from a vague idea to a finished thing through a fixed pipeline, and writes the plan to disk so the work survives between sessions instead of living in one runaway chat.
Who it’s for
Designers and design-leaning builders who are shipping real things in Claude Code and want structure without ceremony. It’s a deliberately small fork — one skill, not an eighty-skill ecosystem — so the overhead stays low and you can read the whole thing.
What it actually does
You start with “build this” and it runs the pipeline:
- Interview — it questions you first to pin down the what, why, who, and what “done” means.
- Spec — that becomes a written
SPEC.mdunder.planning/builds/. - Requirements — traceable requirement IDs, grouped by category.
- Research — parallel agents dig into stack, features, architecture, and risks.
- Roadmap — phases ordered by dependency, with full requirement coverage.
- Per-phase loop — for each phase: discuss the ambiguities, plan, execute, then verify the work actually exists and functions, with auto-retry on fixes.
The opening verb sets how far it runs. “Spec this” or “scope this” stops after the spec. “Draft” or “sketch” stops after the roadmap. “Build” or “ship” runs the whole thing. Two flags shift the mode: --auto runs autonomously on sensible defaults, and --chain talks it through with you, then plans and executes.
Installing
In a Claude Code session:
/plugin marketplace add design-shaped/design-shaped
/plugin install get-stuff-done@design-shaped
This one lives in its own repo and is registered in the Design Shaped marketplace, so the marketplace-add line is the same. After install you’ve got /gsd and /verify. Then just describe what you want to build and pick your verb.