# rqtk

> Requirements that live in your repository, proven by tests. rqtk keeps requirements, stakeholder needs and verification evidence as TOML files next to the code, links tests to requirements, and reports a requirement as verified only when its linked tests passed against its current wording.

Every docs page is available as Markdown by replacing `.html` with `.md`.

## Docs

- [Introduction](https://rqtk.dev/docs/introduction.md)
- [Installation](https://rqtk.dev/docs/getting-started/installation.md)
- [Quick start](https://rqtk.dev/docs/getting-started/quick-start.md)
- [Writing requirements](https://rqtk.dev/docs/guides/requirements.md)
- [Verifying with tests](https://rqtk.dev/docs/guides/verification.md)
- [Baselines and change control](https://rqtk.dev/docs/guides/change-control.md)
- [Coding agents](https://rqtk.dev/docs/guides/agents.md)
- [Continuous integration](https://rqtk.dev/docs/guides/ci.md)
- [Commands](https://rqtk.dev/docs/reference/commands.md)
- [Configuration](https://rqtk.dev/docs/reference/configuration.md)
- [File formats](https://rqtk.dev/docs/reference/file-formats.md)
- [Lint rules](https://rqtk.dev/docs/reference/lint-rules.md)
- [JSON output and exit codes](https://rqtk.dev/docs/reference/json-and-exit-codes.md)
- [Stability](https://rqtk.dev/docs/reference/stability.md)
- [Changelog](https://rqtk.dev/docs/changelog.md)