# First session: document review

On your first session in a project, check if the key documents have
content (not just headings). If a document is empty or only contains
a template structure, offer to fill it together with the user by
working through the checklist below. Ask one question at a time,
write the answer into the document, then move to the next.

## Vision.md checklist
- [ ] What does this product do? (1-2 sentences)
- [ ] Who is the target audience?
- [ ] What are the core features? (bullet list)
- [ ] What are the design principles? (3-5 short statements)
- [ ] What is it NOT? (explicit scope boundaries)
- [ ] What license model applies?

## Architecture.md checklist
- [ ] What is the tech stack? (language, framework, key dependencies with versions)
- [ ] How is the repository structured? (directory tree)
- [ ] How is data stored? (database, files, format)
- [ ] What are the key architectural decisions? (link to ADRs if they exist)
- [ ] What are the performance targets?

## CONTRIBUTING.md checklist
- [ ] What coding conventions apply? (formatting, naming, linting)
- [ ] How are commits structured? (conventional commits, message format)
- [ ] How is testing done? (unit, integration, snapshot, coverage)
- [ ] How is CI/CD configured? (pipeline, triggers, artifacts)
- [ ] What is the branching strategy?

After completing a document, confirm with the user and move to the next.
Skip documents that already have substantial content.
