Lyceum
How it works
Section titled “How it works”-
You describe what you want. The agent works out where it fits in your spec, or whether it’s new.
-
It asks about the things that matter: numbered questions, lettered options, its recommendation first, or your own answer.
-
It proposes the spec change and plan. You approve it or send it back.
-
It builds, then works through gates. A judgment gate waits for your approval. A mechanical gate clears only on a test run the CLI executed and recorded itself.
-
Each acceptance criterion maps to a test, each approval is hashed against what you approved, and
lyceum checkenforces both in the commit hook and in CI.
The agent can say it’s done. Only the CLI can record that it is.
Gates for a feature
Section titled “Gates for a feature”Works with
Section titled “Works with”| Agent | Tested version | Status |
|---|---|---|
| Claude Code | 2.1.318 | ✅ |
| Codex | 0.164.0 | ✅ |
| OpenCode | 2.0.18 | ✅ |
| Pi | 0.86.0 | ✅ |
| Command Code | 1.88.3 | ✅ |
Each was tested end to end in the v1 release check. lyceum init finds the agents you use and installs the skills, slash commands and a hook for each.
Install
Section titled “Install”Run it once without installing:
npx lyceum initnpm i -g lyceumbrew install oritromax/tap/lyceumgo install github.com/oritromax/lyceum/cmd/lyceum@latestSupported platforms are linux-x64, linux-arm64, darwin-x64 and darwin-arm64. Windows isn’t supported. See Install for release downloads.