# Plan repositories

> A plan repository holds a project's engineering records in Fir: plans, specs, decisions, milestones, runbooks and the rest. A record's file is stored in the code repository's own tree or in the project's plan repository, and one index serves both, so every record is numbered, versioned with the code, typed, and linked to the commits, pull requests and checks that implement it without anyone typing a link. Every command is in the Fir CLI reference: https://frazer.ai/docs/source/reference/cli.md.

Part of Frazer's docs for agents. Every page on frazer.ai: https://frazer.ai/llms.txt. Every docs page: https://frazer.ai/docs/llms.txt.

## How agents should use Plan repositories

- Records about this repository are files under `docs/plans/` in your workspace, whether stored in the tree or mounted from the plan repository. Never go to another repository to read a plan; `fir status` says where a new file was stored.
- To learn why a line exists, call `why` (or `fir why <path>:<line>`): the plan version it was written against, the requirements, the decisions in force then and now, the session and what followed.
- You never type a link: your session's binding writes it into every commit. Use `fir plan use <plan>` when a workspace has no plan, and never invent a plan reference.
- Before you write a record of an unfamiliar type, read it with `get_record_type`; a push is never refused for a finding, but new errors block the merge.
- Run `fir record check` on every record you write; it exits non-zero only on an error.
- A plan here is the document a change is written against, not the preview `--dry-run` prints.

## Pages

- [Plan repositories](https://frazer.ai/docs/source/plans.md?from=llms-txt): Plans, specs, decisions, milestones and every engineering document as records in Fir, stored in the code repository's tree or in a plan repository, read through one index, linked to every commit and pull request without anyone typing, and answering why any line of code exists.
- [Record types](https://frazer.ai/docs/source/record-types.md?from=llms-txt): Record types in Fir: any file may live in a plan's home, typed or not; twenty-two built-in types and packs; your own types in YAML with JSON Schema fields and CEL rules, versioned with lossless conversion; made in the editor, by pasting YAML or by asking an agent.

## Optional

- [Full text of these pages](https://frazer.ai/docs/source/plans/llms-full.txt): 2 pages, 69,634 characters, about 17,409 tokens