---
_version: '1'
uuid: a47e8689-cc91-4816-b3e4-9ab0d88d0be8
created: 2025-10-25T16:36:56.468158008Z
parents:
- uuid: 007f03ec-58ff-4cfb-b305-58fcf46be529
fingerprint: 694b343c0aa1e2d40ac2ff3e7805b6caa86fc25876c7dd700182dac26d31ec79
hrid: USR-006
---
# SYS-015 Namespace-Specific Templates
## Statement
The tool shall support configuring different templates for the same KIND but different namespaces, allowing AUTH-USR and USR to have different templates even though both share the KIND 'USR'.
## Implementation Notes
- Namespace-specific templates use full prefix: `{NAMESPACE}-{KIND}.md`
- Example: `.req/templates/AUTH-USR.md` for AUTH namespace USR requirements
- Template lookup tries full prefix first (AUTH-USR.md), then falls back to KIND only (USR.md)
- This allows namespace-specific customization while maintaining default templates
- If both exist, the more specific namespace template takes precedence
- Namespaces enable different teams/domains to customize requirement templates
## Verification
- Creating AUTH-USR requirement uses AUTH-USR.md template if it exists
- Creating AUTH-USR requirement falls back to USR.md if AUTH-USR.md doesn't exist
- Creating USR requirement uses USR.md template
- Namespace-specific template takes precedence over generic template
- Multiple namespaces can coexist with their own templates
- Template lookup logic correctly handles both formats