Report · marked 25 Aug 2026

github/spec-kit

Solid foundations, held back in a few specific places.

Python · 131,448 stars · 545 files · branch main

81 /100 A-

Instructions 25/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 8/16Whether an agent can install the project and get it running without a human. Losing marks on deterministic install and pinned runtime version.Verification loop 22/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on 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

Deterministic install

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

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.

Static type checking

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

The full marking

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

Instructions 25/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: it's 31k characters, which burns context on every single turn.

names the actual commands to run

uses headings, so an agent can skim it

includes copyable code blocks

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 8/16 C+

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

✗Deterministic install 0/6

No lockfile. An agent installing dependencies may not get what CI got.

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

pyproject.toml scripts

–Environment config n/a

Not applicable — this reads as a library, with no environment to configure.

✗Pinned runtime version 0/2

No pinned runtime version.

Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.

✓Reproducible environment 2/2

.devcontainer/devcontainer.json gives a known-good environment.

Verification loop 22/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

165 test files against 308 source files.

e.g. .github/workflows/bug-test.md, extensions/bug/commands/speckit.bug.test.md, presets/self-test/commands/speckit.wrap-test.md

✓Test command is discoverable 7/7

An agent can find and run `pytest`.

✓Continuous integration 4/4

17 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

pyproject.toml encodes the house style.

✗Static type checking 0/3

No static type checking.

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

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 47 patterns.

✗File sizes fit in context 0/6

12 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.

tests/test_workflows.py — 662KB

tests/test_presets.py — 597KB

tests/test_extensions.py — 454KB

✓Repository weight 5/5

About 16.9MB 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 github/spec-kit

# AGENTS.md

💫 Toolkit to help you get started with Spec-Driven Development

## Setup

```
# TODO: the install command. No lockfile was found, so this could not be inferred.
```

## Commands

```
pytest         # run the test suite
ruff check .   # lint
```

## Layout

- `tests/`      157 source files
- `src/`        127 source files
- `scripts/`    12 source files
- `extensions/` 10 source files

## Conventions

- Tests live alongside the code they cover, following `.github/workflows/bug-test.md`.
- CI defines what passing means. See `.github/workflows/add-community-bundle.lock.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `tests/test_workflows.py` is 662KB. It will not fit comfortably in context, so read it in parts.
- No lockfile is committed, so an install here may not match what CI produced.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/github/spec-kit.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](https://agentreadme.com/badge/github/spec-kit.svg)](https://agentreadme.com/github/spec-kit)

Other Python repositories, marked

vinta/awesome-python 81 A- NousResearch/hermes-agent 84 A- TheAlgorithms/Python 66 B yt-dlp/yt-dlp 54 C+ Significant-Gravitas/AutoGPT 63 B microsoft/markitdown 46 C

All Python 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