---
_version: '1'
uuid: 5ff8ed15-2305-4f2a-825f-4f3f0dbe5a53
created: 2025-10-25T16:36:34.489604914Z
parents:
- uuid: 007f03ec-58ff-4cfb-b305-58fcf46be529
fingerprint: 694b343c0aa1e2d40ac2ff3e7805b6caa86fc25876c7dd700182dac26d31ec79
hrid: USR-006
---
# SYS-011 Template File Storage
## Statement
The tool shall support defining templates as individual markdown files in the `.req/templates/` directory, with each template file named after its requirement kind.
## Implementation Notes
- Templates stored in `.req/templates/` directory (e.g., `.req/templates/USR.md`)
- Template filename must match requirement kind: `{KIND}.md`
- Namespace-specific templates use full prefix: `{NAMESPACE}-{KIND}.md`
- Template files contain plain markdown content
- Tool loads templates from filesystem when creating requirements
- Template directory is excluded from requirement scanning
## Verification
- Templates are successfully loaded from `.req/templates/` directory
- Template filenames correctly map to requirement kinds
- Namespace-specific templates (e.g., AUTH-USR.md) are recognized
- Template content is correctly inserted into new requirements
- Templates directory doesn't interfere with requirement loading