llms.txt
Compare with other sites' llms.txt files →# SLCR
> SLCR is an open standard for spec-driven development: software requirements that coding agents read in slices and tools check against your code.
SLCR stands for Sliceable, Linked, Checkable Requirements. A project's requirements live in one structured specification file (TOML, YAML, or JSON). Agents read small, task-specific excerpts of it called slices, people read a Markdown document rendered from it, and validators in the codebase check whether the code meets each requirement.
The reference implementation is the `slcr` CLI, written in Rust and released under the MIT License: https://github.com/wack/slcr
The full text of every doc page is at https://slcr.dev/llms-full.txt.
## Overview
- [Overview](https://slcr.dev/docs/overview): What SLCR is, the problems it addresses, and how specifications, slices, and validators fit together.
- [Use cases](https://slcr.dev/docs/use-cases): What SLCR is used for, from building with coding agents to catching drift in CI, and when it isn't a good fit.
- [FAQ](https://slcr.dev/docs/faq): Answers to common questions about SLCR: whether it's ready, what it costs, which languages and platforms it supports, and how to use it with coding agents.
## Getting started
- [Installation](https://slcr.dev/docs/getting-started/installation): Install the `slcr` CLI and the agent skill, keep them up to date, and install them in CI.
- [Quickstart](https://slcr.dev/docs/getting-started/quickstart): Set up SLCR in an existing project with a coding agent, and see which requirements your code already meets.
- [Tutorial: write a small SLCR specification](https://slcr.dev/docs/getting-started/tutorial): Learn SLCR by writing a small specification, checking it with validators, and seeing requirements go from unsatisfied to satisfied.
## Concepts
- [Specifications](https://slcr.dev/docs/concepts/specifications): How SLCR stores requirements as a graph, the four kinds of node, permanent IDs, and how specs make up a project.
- [Links and satisfaction](https://slcr.dev/docs/concepts/links-and-satisfaction): How requirements connect to each other, and how those links decide whether each requirement is satisfied.
- [Slices](https://slcr.dev/docs/concepts/slices): What a slice contains, what it leaves out, and how slicing affects the way a spec is written.
- [Validators](https://slcr.dev/docs/concepts/validators): How acceptance criteria, validators, and tools turn requirements into checks that pass or fail, and the difference between vetting and checking.
## Guides
- [Writing requirements](https://slcr.dev/docs/guides/writing-requirements): How to write requirements that are checkable and slice well: one testable statement each, the right modality, explicit links, and a sliceable structure.
- [Migrating existing documents](https://slcr.dev/docs/guides/migrating): Convert an existing requirements document to SLCR with a coding agent, then review and verify the result.
- [Add a validator tool](https://slcr.dev/docs/guides/add-a-validator-tool): Declare a tool in a project, write validators for it, and keep its descriptor up to date.
- [Run SLCR in CI](https://slcr.dev/docs/guides/run-in-ci): Check a project's specifications, rendering, and validators on every change, with the SLCR GitHub Action or any CI system.
- [Troubleshoot `slcr check`](https://slcr.dev/docs/guides/troubleshoot-slcr-check): What each `slcr check` failure means and how to fix it: vetting errors, red validators, unsatisfied or unknown requirements, and CI-only failures.
## Reference
- [Specification](https://slcr.dev/docs/reference/specification): The normative definition of the SLCR specification file format: files, IDs, sections, requirements, acceptance criteria, links, and vet findings.
- [Project manifest](https://slcr.dev/docs/reference/project-manifest): The normative definition of SLCR.toml, the file that marks a project's root and declares its specifications and tools.
- [Validator files](https://slcr.dev/docs/reference/validator-files): The normative definition of validator files, which tie requirements to the tools that check them.
- [Tool descriptors](https://slcr.dev/docs/reference/tool-descriptors): The normative definition of tool descriptors, which describe how SLCR runs the tools validators use.
- [CLI](https://slcr.dev/docs/reference/cli): Every `slcr` command, from `init` and `check` to `slice` and `render`, with its arguments, options, and exit codes.
## Optional
- [About SLCR](https://slcr.dev/about): Why SLCR exists, who maintains it, how changes to the standard are decided, and how you can contribute.
- [Announcements](https://slcr.dev/announcements): News and release updates for SLCR, the open standard for agent-native software requirements, and its reference CLI.
- [Code of Conduct](https://slcr.dev/code-of-conduct): How we expect everyone in the SLCR community to behave, how to report a problem, and how maintainers enforce this code.
- [Security](https://slcr.dev/security): Which SLCR versions get security fixes, how to report a vulnerability privately, and what's in scope.