Skip to content

docs: launch README, demo scripts, and issue templates - #35

Open
hefgi wants to merge 5 commits into
mainfrom
gtm/readme-and-launch-content
Open

hefgi wants to merge 5 commits into
mainfrom
gtm/readme-and-launch-content

Conversation

@hefgi

@hefgi hefgi commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Summary

Launch content, rebased onto main after #32, #33, and #34.

Docs and templates only, no code changes.

hefgi added 5 commits October 2, 2026 16:04
The README opened with an infrastructure description ("ephemeral local
environments") which reads as a category nobody searches for. Lead with the
problem instead: agents can't verify work they can't run.

- Rewrite README and docs intro around the verification framing
- Add an honest comparison table vs Superset/claude-squad/Gastown/ccmanager/cmux,
  positioning them as complements rather than competitors
- Move the full config reference to the docs site; keep a typical example inline
- Document the previously undocumented per-service `compose` field, plus a
  monorepo example, so nothing is lost from the README slim-down
- Add GIF placeholder above the fold
Two assets: a 30s silent GIF for the README hero, and a 90s narrated video
showing an agent catching its own bug because it had an environment to verify in.

Includes tooling setup, shot lists, the bug to plant (missing migration — passes
unit tests, fails e2e), and a verification checklist.
Detection getting a repo wrong is a bug, not user error — the stack_support
template makes those reports easy to file and easy to act on. Points questions
at Discussions rather than issues.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant