Browse / Software development / buildomator
buildomator
buildomator
Structured plan/execute/verify coding workflow for Claude Code: atomic commits, MCP-backed state, 92% lower per-turn token overhead, native convention + drift-detection safeguards, and an ASD-STE100 (Simplified Technical English) anti-slop docs gate.
Open buildomator/buildomator → Does not match the four rules.
ai-coding-agentsai-slopanti-slopasd-ste100claude-codecode-gecoding-workflowcontext-engineeringdeveloper-toolsdrift-detectionmcpsimplified-technical-english
Built for one agent
ships CLAUDE.md and nothing for other agents.
In its own words
A Claude Code-native evolution of GSD and VibeDrift.
Buildomator (formerly gsd-plugin) is a Claude Code plugin that plans, executes, and verifies your work. It asks you only about the real design and architecture decisions that need your judgment, then carries out the rest on its own. Each step runs in its own focused subcontext, so token use stays low even on long projects.
Buildomator is a performance-optimized evolution of GSD for Claude Code: it cuts per-turn token overhead by ~92%, keeps project state in an MCP-backed store, and auto-resumes across /compact so a compaction never loses your place.
Project home and docs: buildomator.com.
Installation
GSD Plugin installs inside a Claude Code session, not from your host shell. If you have never used Claude Code plugins before, follow these steps in order.
No prerequisites
As of v2.42.0 the plugin bundles its own copy of the GSD SDK at sdk/dist/cli.js and ships a bin/bm-sdk wrapper (plus a bin/gsd-sdk alias) that Claude Code automatically puts on PATH for plugin Bash calls. bm-sdk is the primary command name; gsd-sdk keeps working as a fully equivalent alias through the 4.x line and retires at v5.0 on 2026-10-01. You no longer need to npm install -g get-shit-done-cc (or its successor get-shit-done-redux). Closes #4.
The repository's own description, then 4% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.