Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
GSD (Get Shit Done) / GSD Core
Meta-prompting and context-engineering framework running discuss -> plan -> execute -> verify -> ship per phase, with heavy work in fresh-context subagents. Continued by a community org after the original was archived.
Original gsd-build/get-shit-done (~64k stars) archived, last push 2026-05-31, README redirects to community-run open-gsd/gsd-core (created 2026-05-22); gsd-core v1.18.0 released 2026-10-19 (checked 2026-10-25)
In Spec-driven development
What it shares with most of the community
- Is it actively maintained? active (74% of 19 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (74% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (74% of 19 others)
- Who is it for? developers (100% of 19 others)
- Once code exists, what is the spec? a planning scaffold: code becomes the truth after implementation (53% of 19 others)
- What format are specs written in? markdown from templates or free-form (67% of 18 others)
- Where do specs live? plain files in the project repository (89% of 19 others)
- Which coding agents does it work with? many agents (five or more) (78% of 18 others)
- How is the path from idea to code structured? a fixed sequence of phases (e.g. requirements, design, tasks) (53% of 19 others)
- What does it offer teams beyond sharing files in git? (if both, pick the paid product) nothing beyond git (50% of 18 others)
Not documented
The public sources we read don't say:
- How is it mainly sustained?
Nearest neighbors
- Agent OS 81% of 16 shared answers match
- PRP (Product Requirement Prompts) 81% of 16 shared answers match
- Superpowers 81% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active Active as a community fork; the original project is archived. | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) MIT | source 2026-10-25 |
| How is it mainly sustained? | Not documented Small crew, open source; no pricing, sponsors or funding found; a cloud product is planned. Unsettled. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account npx installer into your agent runtime; no sign-up. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Installer writes its own commands and agents per runtime; planning files are its own. | source 2026-10-26 |
| Once code exists, what is the spec? | a planning scaffold: code becomes the truth after implementation | source 2026-10-25 |
| After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) | a step checks code against the spec (tests, review, or verifier) Verify step: 'walk through what was built; diagnose and fix'. | source 2026-10-25 |
| What format are specs written in? | markdown from templates or free-form | source 2026-10-25 |
| Where do specs live? | plain files in the project repository | source 2026-10-25 |
| Which coding agents does it work with? | many agents (five or more) Claude Code, OpenCode, Antigravity, Kimi, Kilo, Codex, Copilot, Cursor, Windsurf. | source 2026-10-25 |
| What form does it mainly ship in? | prompts, skills, or slash commands installed into an agent (even if a CLI installs them) npx installer for commands and agents. | source 2026-10-25 |
| How is the path from idea to code structured? | a fixed sequence of phases (e.g. requirements, design, tasks) Discuss -> Plan -> Execute -> Verify -> Ship per phase. | source 2026-10-25 |
| Does a human approve the spec or plan before code is written? | review is recommended but not enforced Discuss step captures decisions; approval not confirmed as enforced. | source 2026-10-25 |
| By default, once a plan is approved, how is implementation run? | agents run the whole plan with automated review or verification loops Executes plans in parallel waves of fresh-context subagents. | source 2026-10-25 |
| What does it offer teams beyond sharing files in git? (if both, pick the paid product) | nothing beyond git | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/open-gsd/gsd-core · read 2026-10-25
- GitHub · github.com/open-gsd/gsd-core/releases · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.