agentreadme

Report · marked 25 Aug 2026

gsd-build/get-shit-done

Ready for an agent to work in without hand-holding.

JavaScript · 64,643 stars · 1,854 files · branch main

85 /100 A
Instructions 23/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality and readme as an entry point.Setup 14/14Whether an agent can install the project and get it running without a human. Full marks.Verification loop 21/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules and static type checking.Context economy 14/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

01
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
02
README as an entry point
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
03
Lint and format rules
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

The full marking

Every deduction below names the file or setting it came from.

Instructions 23/27 A

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12
AGENTS.md is present, which is the format the most tools read.
✗Instruction quality 10/12
Specific enough that an agent can act on it.
Worth fixing: has no code blocks.
3,075 characters, a workable length
names the actual commands to run
uses headings, so an agent can skim it
✗README as an entry point 1/3
README exists but never explains how to get the thing running.
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
Setup 14/14 A+

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6
package-lock.json pins the dependency tree.
Found package-lock.json
✓Discoverable commands 6/6
Commands are declared where an agent will look for them.
package.json scripts (build:hooks, build:sdk, check:alias-drift, check:state-document-fresh, check:configuration-fresh, check:workstream-inventory-builder-fresh…)
scripts/ directory
–Environment config n/a
Not applicable — this reads as a library, with no environment to configure.
✓Pinned runtime version 2/2
The language runtime version is pinned.
package.json engines.node >=22.0.0
–Reproducible environment n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 21/25 A-

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8
719 test files against 994 source files.
e.g. docs/ja-JP/superpowers/specs/2026-03-20-multi-project-workspaces-design.md, docs/ko-KR/superpowers/specs/2026-03-20-multi-project-workspaces-design.md, docs/pt-BR/superpowers/specs/2026-03-20-multi-project-workspaces-design.md
✓Test command is discoverable 7/7
An agent can find and run `npm run test`.
✓Continuous integration 4/4
20 GitHub Actions workflows define what "passing" means.
✗Lint and format rules 0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
✗Static type checking 2/3
Type checking is configured, but not in strict mode.
Turn on `"strict": true`. Type errors are the fastest feedback an agent gets, and non-strict mode silently discards most of them.
Context economy 14/20 B+

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6
No generated directories committed.
✓.gitignore hygiene 3/3
.gitignore covers 58 patterns.
✗File sizes fit in context 0/6
5 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
bin/install.js — 463KB
tests/phase.test.cjs — 173KB
sdk/src/phase-runner.test.ts — 152KB
✓Repository weight 5/5
About 20.3MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for gsd-build/get-shit-done 
undefined

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/gsd-build/get-shit-done.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

agent ready 85 out of 100

[![agent ready](https://agentreadme.com/badge/gsd-build/get-shit-done.svg)](https://agentreadme.com/gsd-build/get-shit-done)

Other JavaScript repositories, marked

react/react 71 B+ affaan-m/ECC 90 A trekhleb/javascript-algorithms 69 B Snailclimb/JavaGuide 53 C+ airbnb/javascript 54 C+ vercel/next.js 77 B+

All JavaScript repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in