SLCR
SLCR lets software teams define linked, checkable requirements and give AI coding agents task-specific slices. Teams connect acceptance criteria to validators and use the CLI to check requirement status, including in CI.
Who it's for
- Software teams using AI coding agents that need to give each agent only the requirements relevant to its task.
- Developers maintaining specifications in JSON, TOML, or YAML who want requirements linked to acceptance criteria and validators.
- Teams that want to run requirement checks alongside their existing tests, linters, browser tests, or CI workflows.
How it fits your workflow
Write requirements in JSON, TOML, or YAML. Link requirements that refine or depend on one another so a task-specific slice can include its relevant context.
Attach declared validators to acceptance criteria. The page names tests, linters, browser tests, agents, and ast-grep as examples.
Run `slcr check` to see which requirements are met; the page also describes running checks in CI.
Pricing
The vendor doesn't publish prices. Check with SLCR directly.
Prices checked on Oct 31, 2026 from the vendor's site. They can change; confirm before you buy.
Key features
- Requirement slicing
- Provide agents with a task-relevant requirement and its linked context while keeping unrelated parts of the specification out of the agent's context.
- Linked requirements
- Requirements can refine or depend on other requirements and can be combined using AND, OR, and XOR.
- Checkable acceptance criteria
- Acceptance criteria can be mapped to declared validators, including tests, linters, browser tests, and agents.
- CLI checks
- The `slcr check` command reports which requirements are met; the page shows checks being run in CI.
- Multiple specification formats
- The page shows requirements written in YAML and states that JSON, TOML, and YAML are supported.
- Agent skill
- An agent skill teaches agents to write SLCR requirements and use the CLI.
Works with
- Validator tools
- ast-grep
- CI
Alternatives to consider
-
Spec-first
Choose it if you want a guided workflow from a repository-grounded specification through review, implementation, checks, and pull request delivery rather than SLCR's open requirements standard and validator-focused CLI.
Getting started
slcr init- Follow the getting-started quickstart linked from the project page.
- Initialize the project with `slcr init`.
- Write requirements and acceptance criteria, then attach validators.
- Run `slcr check` to review which requirements are met.