From 69c3df224eed647401b7225dcd8618690553936b Mon Sep 17 00:00:00 2001 From: GX Xu Date: Fri, 8 May 2026 17:32:53 -0400 Subject: [PATCH 1/2] docs: add GSD comparison section to README Co-Authored-By: Claude Opus 4.6 (1M context) --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 045c016..6e6b733 100644 --- a/README.md +++ b/README.md @@ -293,6 +293,16 @@ Built something with the Factory? Open a PR to add it here — it helps others s --- +## How It Compares to GSD + +[Get Shit Done (GSD)](https://github.com/gsd-build/get-shit-done) is a great tool that tackles the same problem — turning ideas into working software with AI. Having used both extensively, here's where the Factory differentiates: + +- **One command, not many.** GSD asks you to run the same discuss/plan/execute sequence for each phase. The Factory's CEO agent owns the full lifecycle — you give it a spec and come back to working software. +- **Self-verification that works.** Both tools have verification stages, but GSD often punts things to the human that it could check itself. The Factory's eval-and-revert loop is the core of the system — every change is scored, and regressions are automatically reverted. The result: what you get back has already been extensively verified by agents and just works. +- **High-level steering, not per-phase commands.** The Factory takes direction at the level humans naturally think — "add dark mode", "improve performance" — and decomposes it internally. You steer via `--focus`, backlog items, or GitHub issues, not by babysitting each phase. + +--- + ## Live Dashboard Monitor factory activity in real time with `factory dashboard`: From de3ee0c2596a9b0953718fad3bc9cadb1e88967e Mon Sep 17 00:00:00 2001 From: GX Xu Date: Mon, 11 May 2026 11:31:20 -0400 Subject: [PATCH 2/2] docs: reframe GSD comparison as motivation in README intro Move from standalone comparison section to a short motivation paragraph at the top. Softer tone, focuses on why the Factory exists rather than what's wrong with alternatives. Co-Authored-By: Claude Opus 4.6 (1M context) --- README.md | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 6e6b733..436abf5 100644 --- a/README.md +++ b/README.md @@ -9,6 +9,8 @@ **Describe what you want. The Factory builds it, tests it, and keeps improving it — autonomously.** You give it a spec file, a rough idea, or an existing codebase. The Factory researches best practices, scaffolds the project, sets up evaluation, and runs a continuous improvement loop — measuring every change and keeping only what makes things better. +**Why we built this.** Existing AI coding tools like [GSD](https://github.com/gsd-build/get-shit-done) are powerful, but they often require repetitive manual steps and hand verification at every phase. The Factory was built to minimize that — agents verify their own work, and what you get back just works. + --- ## Quick Start @@ -293,16 +295,6 @@ Built something with the Factory? Open a PR to add it here — it helps others s --- -## How It Compares to GSD - -[Get Shit Done (GSD)](https://github.com/gsd-build/get-shit-done) is a great tool that tackles the same problem — turning ideas into working software with AI. Having used both extensively, here's where the Factory differentiates: - -- **One command, not many.** GSD asks you to run the same discuss/plan/execute sequence for each phase. The Factory's CEO agent owns the full lifecycle — you give it a spec and come back to working software. -- **Self-verification that works.** Both tools have verification stages, but GSD often punts things to the human that it could check itself. The Factory's eval-and-revert loop is the core of the system — every change is scored, and regressions are automatically reverted. The result: what you get back has already been extensively verified by agents and just works. -- **High-level steering, not per-phase commands.** The Factory takes direction at the level humans naturally think — "add dark mode", "improve performance" — and decomposes it internally. You steer via `--focus`, backlog items, or GitHub issues, not by babysitting each phase. - ---- - ## Live Dashboard Monitor factory activity in real time with `factory dashboard`: