golem15/msd-core
3
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs: reorder README sections for better flow

Browse Source
This commit is contained in:
Lex Christopherson
2026-01-06 11:51:08 -06:00
parent 21d88476f9
commit 65df2f45f0
1 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
README.md
View File

@@ -27,6 +27,28 @@ GSD fixes that. It's the context engineering layer that makes Claude Code reliab
---
## Who This Is For
People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.
---
## Why I Built This
I'm a solo developer. I don't write code — Claude Code does.
Other spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work.
So I built GSD. The complexity is in the system, not in your workflow. Behind the scenes: context engineering, XML prompt formatting, subagent orchestration, state management. What you see: a few commands that just work.
The system gives Claude everything it needs to do the work _and_ verify it. I trust the workflow. It just does a good job.
That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.
— TÂCHES
---
## Installation
```bash
@@ -48,22 +70,6 @@ Verify: `/gsd:help`
---
## Why I Built This
I'm a solo developer. I don't write code — Claude Code does.
Other spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work.
So I built GSD. The complexity is in the system, not in your workflow. Behind the scenes: context engineering, XML prompt formatting, subagent orchestration, state management. What you see: a few commands that just work.
The system gives Claude everything it needs to do the work _and_ verify it. I trust the workflow. It just does a good job.
That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.
— TÂCHES
---
## How It Works
### 1. Start with an idea
@@ -248,12 +254,6 @@ You're never locked in. The system adapts.
---
## Who This Is For
People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.
---
## License
MIT License. See [LICENSE](LICENSE) for details.