Workspine — plan, execute, and verify AI-assisted work from files in your repo, with proof before done. Published as gsdd-cli.
Workspine is a Spec Driven Development framework for AI-assisted software work: planning, checking, execution, verification, and handoff live in the repo, so any agent or runtime can pick up where the last one stopped. Decisions keep their why.
Proof status: one real consumer lifecycle with Codex checker support. Qualified support: Cursor, Copilot, Gemini.
The public product name is Workspine. The retained technical contracts remain gsdd-cli, gsdd, gsdd-*, and .work/.
npx -y gsdd-cli init
Use npx -y gsdd-cli init for repo-local setup. Use npx -y gsdd-cli install --global --auto to install reusable Workspine skills and native runtime surfaces into detected agent homes so they are available across repos.
Tracked consumer proof pack: docs/proof/consumer-node-cli/README.md
init places workflow skills in .agents/skills/ and optionally native adapters for your runtime. Then you run workflows through your agent — each one writes files to the repo:
| Workflow | Writes | What for |
|---|---|---|
gsdd-new-project | .work/SPEC.md, ROADMAP.md | Define the project and phases |
gsdd-plan | .work/phases/N/PLAN.md | Research and review before any code gets written |
gsdd-execute | .work/phases/N/SUMMARY.md | Implement the approved plan, nothing more |
gsdd-verify | .work/phases/N/VERIFICATION.md | Confirm the plan's claims are actually true |
The discipline: plan first, execute only what's approved, verify before closing. Each phase summary carries forward what was decided, so the next session starts with context instead of from scratch.
For agent continuity across long sessions, gsdd next reads .work/ plus repo truth and emits the next coherent action as a structured packet. Use gsdd next --init to bootstrap .work; plain gsdd next is read-only. Captured stdout defaults to JSON; use gsdd next --format human for the compact supervisor card.
gsdd next keeps the human surface tight and the agent surface structured. JSON packets include typed next_action values for CLI commands, workflow skills, manual review, and user-question gates. Blocking questions, decisions, graph rebuilds, and dogfood findings use explicit subcommands; duplicate question, decision, and dogfood IDs replay as unchanged when the content matches and fail unless --replace is passed when the content differs. The continuity graph records answer and supersession edges so future agents can reconstruct decision history without rereading raw transcripts.
Workspine ships 13 workflows. The package and CLI are gsdd-cli / gsdd-* — retained as the technical contract under the Workspine product name.
Workspine gives coding agents a durable workflow for work that spans sessions, agents, or runtimes. There is no hosted service; it writes portable planning and proof artifacts into the repo.
Workspine began as a fork of Get Shit Done and keeps the verification-first workflow while stripping runtime lock-in.
npx -y gsdd-cli init
This creates:
.work/ — durable workspace with templates, role contracts, and config.agents/skills/gsdd-* — compact open-standard workflow entrypoints for agents.work/bin/gsdd.mjs — repo-local helper runtime for deterministic workflow commands inside generated skills (run helper commands from the repo root)Then pick the first workflow lane that matches your situation:
gsdd-new-project for greenfield work, fuzzy brownfield work, or milestone-shaped workgsdd-quick for a concrete bounded brownfield changegsdd-map-codebase first when the repo is unfamiliar, risky, or needs a deeper baseline before choosing a laneIn a terminal, npx -y gsdd-cli init opens a guided install wizard. If you installed the package globally, gsdd init is the equivalent shorthand:
AGENTS.md governance is worth installingPortable .agents/skills/gsdd-* skills and the repo-local .work/bin/gsdd.mjs helper runtime are always generated. The wizard controls extra native adapters and optional governance, not the portable baseline. Workflow helper commands assume the repo root as the current working directory.
When those generated surfaces exist locally, npx -y gsdd-cli health checks them against current render output instead of asking you to trust manual review. If installed globally, gsdd health is equivalent.
.agents/skills/ surface when their skill or slash discovery sees it; this release does not claim the same runtime proof or ergonomics.npx -y gsdd-cli update or, when globally installed, gsdd update.Start with the public proof pack:
Invoke after init:
/gsdd-plan.gsdd-plan skill reference ($gsdd-plan), with .codex/agents/gsdd-plan-checker.toml for native checker isolation..agents/skills; if it does not, open .agents/skills/gsdd-<workflow>/SKILL.md.Headless setup is available for CI or scripted installs:
npx -y gsdd-cli init --auto --tools all
npx -y gsdd-cli init --auto --tools codex --brief path/to/brief.md
If gsdd-cli is installed globally, install reusable Workspine surfaces into your agent homes:
npx -y gsdd-cli install --global
npx -y gsdd-cli install --global --auto
npx -y gsdd-cli install --global --tools claude,opencode,codex,copilot
Use --auto for non-interactive install into detected local agent homes. Use --tools <targets> when you want to override detection explicitly. When run in a TTY without --tools or --auto, install --global lets you select which agents to install. It does not create .work/ in the current repo. It writes Workspine-managed skills, native agent surfaces, and per-runtime manifests under the selected agent homes:
| Target | Global surfaces |
|---|---|
| Claude Code | ~/.claude/skills, ~/.claude/commands, ~/.claude/agents |
| OpenCode | ~/.agents/skills, ~/.config/opencode/commands, ~/.config/opencode/agents |
| Codex CLI | ~/.agents/skills, ~/.codex/agents |
| GitHub Copilot CLI | ~/.agents/skills, ~/.copilot/agents |
Install availability is not a parity claim. Repo proof currently covers Claude Code, OpenCode, and Codex CLI paths; GitHub Copilot CLI is available as a qualified global target.
OpenCode honors OPENCODE_CONFIG_DIR for commands and agents; Workspine installs portable skills once in the shared agent-compatible global root.
| Situation | Start here |
|---|---|
| New project, or brownfield work that's broad / milestone-shaped | gsdd-new-project — full initializer, runs codebase mapping internally when needed |
| Existing repo, and the change you want to make is already concrete | gsdd-quick — bounded-change lane, lighter ceremony |
| Existing repo is unfamiliar or risky and you want a baseline first | gsdd-map-codebase — orientation pass before choosing the above |
Commit .work/ so the team shares specs, roadmaps, phase plans, and verification reports. Use commitDocs in .work/config.json to control whether documentation changes are expected as part of workflow execution. Each developer runs init --tools <their-tool> for their own repo-local runtime adapters without changing the shared delivery artifacts.
Track .work/, .agents/skills/, and any selected runtime adapters that are part of the team workflow. Track durable .work/ contract and research files when they define shared milestone truth. Do not track .work/.local/ or mutable .work runtime files such as state.json, graph logs, open questions, evidence manifests, handoff notes, or raw dogfood drafts unless you deliberately export or sanitize them.
Use model profiles to tune cost and rigor:
npx -y gsdd-cli models profile quality # maximize rigor
npx -y gsdd-cli models profile balanced # default balance
npx -y gsdd-cli models profile budget # minimize cost
Inside a repo-local .work/ workspace, start with npx -y gsdd-cli health. It checks local generated runtime surfaces against current render output and reports whether npx -y gsdd-cli update can repair drift. To repair or refresh a personal global install, rerun npx -y gsdd-cli install --global --auto or explicitly scope it with npx -y gsdd-cli install --global --tools <targets>. For details, see the User Guide.
Use Workspine when a feature takes more than one session, or when you need to switch between Claude, Codex, and Cursor without losing the thread. Skip it for quick, obvious edits — direct prompting is cheaper when the risk is small.
| Tool | Good for | vs Workspine |
|---|---|---|
| Workspine | Work that spans sessions, agents, or runtimes where plans and proof need to stay in the repo | — |
| GSD | Broad AI prompting suite — 81 commands, 78 workflows, 33 agents | Workspine is narrower: 13 workflows, fewer moving parts for the human in the loop |
| OpenSpec | Living spec + change proposals in a lightweight format | Workspine adds the execution, verification, and handoff layer on top of planning |
| LeanSpec | Minimal specs that fit LLM context | Workspine adds workflow gates and runtime entrypoints for when you need the full structure |
| GitHub Spec Kit | Spec-first planning workflows in .specify/ | Similar space; Workspine is one CLI with one delivery loop instead of a broader ecosystem |
| Kiro | IDE-native agent dev with specs, steering, hooks, and MCP | Kiro is IDE-only; Workspine works across terminal and IDE agents that can read repo files |
| Tessl | Hosted platform for distributing agent skills across teams | Tessl needs a hosted service; Workspine is local-first with no hosted infrastructure |
Based on each tool's public docs as of May 2026. Open an issue if anything reads inaccurately.
npx -y gsdd-cli health # workspace integrity check
npx -y gsdd-cli update # regenerate stale runtime surfaces
npx -y gsdd-cli update --templates # refresh runtime surfaces and template payloads
npx -y gsdd-cli next --json # read .work continuity and emit the next action packet
npx -y gsdd-cli next --format human # show the compact supervisor card
npx -y gsdd-cli next --init # bootstrap .work continuity state explicitly
npx -y gsdd-cli journey # show the milestone and phase delivery journey, including decisions and mistakes # (experimental)
npx -y gsdd-cli remember "Use direct commits" --type rule --scope repo # (experimental)
npx -y gsdd-cli decisions query "current git flow" --path bin/gsdd.mjs # (experimental)
npx -y gsdd-cli decisions promote <id> # (experimental)
npx -y gsdd-cli decisions reject <id> --reason "No longer applicable" # (experimental)
npx -y gsdd-cli decisions invalidate <id> --reason "Superseded by the current policy" # (experimental)
npx -y gsdd-cli rigor # run planning/document guardrails
npx -y gsdd-cli file-op # deterministic repo-local copy/delete helper
npx -y gsdd-cli models profile quality # maximize review rigor
npx -y gsdd-cli models profile budget # minimize cost
npx -y gsdd-cli find-phase # locate a roadmap phase
npx -y gsdd-cli phase-status # inspect or update phase status
npx -y gsdd-cli verify # run verification discipline checks
npx -y gsdd-cli scaffold # scaffold planning surfaces
npx -y gsdd-cli help # print command help
Full reference: User Guide · Runtime Support · Verification Discipline
Fork of Get Shit Done by Lex Christopherson, MIT licensed. Original git history retained.
MIT License. See LICENSE for details.
FAQs
Workspine — plan, execute, and verify AI-assisted work from files in your repo, with proof before done. Published as gsdd-cli.
The npm package gsdd-cli receives a total of 144 weekly downloads. As such, gsdd-cli popularity was classified as not popular.
We found that gsdd-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Benign-looking npm packages split malicious functionality across a dependency chain that deploys a cross-platform RAT targeting Alibaba developers.
Research
/Security News
Two Joyfill npm beta releases contain an import-time implant that uses blockchain transactions to retrieve a remote-access trojan.
Security News
Socket releases free Certified Patches for high-severity Nuxt vulnerabilities, including server-side remote code execution through server island props.