UniClipboard
drift: noneLocal-first, end-to-end-encrypted clipboard sync tool in Rust whose .planning/ tree is a heavily used working GSD instance — five completed milestone cycles with per-phase plan, progress, and findings docs.
GSD (Get Shit Done) emerging
Context-engineering-first SDD loop — fresh-context subagents, persistent state artifacts, and phase-gated milestones — continued by the community OpenGSD org after the original repo was archived.
Reviewed 2 months ago · Jul 18, 2026
Website GitHub · open-gsd/gsd-core Compare with other frameworks →
- Stars
- 9K
- Contributors
- 166
- Open issues
- 157
- Age
- 3 months
- Last push
- today
- Latest release
- v1.12.0 Aug 30, 2026
Metrics updated Sep 1, 2026 · collected automatically from the GitHub API
Core approach
Treats context rot as the core failure mode of long agent sessions. Work is broken into milestone phases executed by fresh-context subagents in parallel git worktrees, while continuity lives in structured artifacts like STATE.md and CONTEXT.md rather than in the conversation itself. A Node CLI installs the same hyphen-style slash-command workflow into a dozen-plus runtimes.
Workflow
/gsd-new-project— interactive setup with research, requirements, and roadmap (or/gsd-onboardfor existing codebases)/gsd-discuss-phase— lock implementation preferences and assumptions/gsd-plan-phase— research, planning, and feasibility verification/gsd-execute-phase— parallel execution in isolated worktrees with clean contexts/gsd-code-review— structured review before human verification/gsd-verify-work— manual UAT of the built work/gsd-ship— create the pull request and archive the phase/gsd-complete-milestone— audit requirements coverage, tag, and finalize
Supported tools
- Claude Code
- GitHub Copilot
- OpenCode
- Cursor
- Windsurf
- Cline
- Codex
- Qwen Code
- Kilo
- CodeBuddy
- Augment
- Antigravity
- Trae
- Hermes
Strengths
- Context engineering is the product: fresh-context subagents plus
STATE.md/CONTEXT.mdcontinuity directly target context rot, which most other kits ignore - Covers the full loop from idea to PR — research, planning, parallel worktree execution, code review, UAT, and shipping
- One
npxinstaller deploys the same workflow across 14 runtimes, with router bundles for tools that can't nest skills - Growing companion ecosystem under the OpenGSD org —
gsd-browserfor verification evidence,gsd-pias a standalone harness
Limitations
- Governance churn: the original repo (
gsd-build/get-shit-done, ~65k stars) was archived in June 2026, and the community is still consolidating around thegsd-corecontinuation - Large command surface (~30 slash commands) with its own vocabulary of milestones, phases, seeds, and threads — a real learning curve
- The Node.js/
npxinstaller is mandatory; manually copying files between runtimes is unsupported - Claude Code-first heritage shows — several runtimes need namespace-router workarounds for non-recursive skill loading
Tracked projects using GSD (Get Shit Done)
Notes
GSD is the observatory’s clearest governance case study. The original repo by TÂCHES went from creation in December 2025 to roughly 65k stars in six months — the fastest rise of any SDD tool we track — and was then archived in June 2026, with development handed to the community OpenGSD org, whose site now states that “trust is part of the product”. Its thesis also stands apart: where Spec Kit treats the spec as the durable artifact, GSD treats context as the scarce resource, and its state files exist so that agents survive session resets. GitHub code search finds 140-odd public repos carrying GSD state files; whether that adopter base follows the star count to the new repo is exactly what the metrics here are for.