> ## Documentation Index
> Fetch the complete documentation index at: https://docs.specpilot.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The .specs folder

> Everything SpecPilot knows about your project lives in plain files inside your repo.

`.specs/` sits at the root of your repo and goes into git with your code. It holds Markdown and YAML files, so any editor can open them and any agent can read them. Your agent reads them at the start of a session and keeps them current as it works. The SpecPilot App shows them; the only file it changes is your task list.

| File | What it holds |
| - | - |
| `README.md` | What the folder is and how it is organised |
| `project/project.yaml` | Project settings: name, stack and where the specs live |
| `project/requirements.md` | Functional and non-functional requirements, with REQ IDs |
| `architecture/architecture.md` | System design, components and decisions (ADRs) |
| `architecture/api.yaml` | API endpoints, only for projects that have an API |
| `planning/tasks.md` | Your tasks, which the App shows as a board |
| `planning/roadmap.md` | Milestones and what goes into each |
| `development/context.md` | Key decisions and known issues |
| `development/prompts.md` | A log of the prompts that shaped the project |
| `development/onboarding.md` | How to start work on the project, written for a new or an existing codebase |
| `quality/tests.md` | Test strategy and test cases |
| `security/threat-model.md` | Threats and how they are handled |
| `security/security-decisions.md` | Security decisions and their reasons |

That is 13 files, or 12 for a project without an API.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.