Add a requirement (functional or non-functional)
COMMAND: Add a requirement to specs. Auto-detect type from description.
| Input contains | Type | File |
|---|---|---|
| "users can", "should be able to" | FR | docs/specs/features/[name].md |
| "P95", "latency", "under Xms" | NFR | docs/specs/non-functional/performance.md |
| "uptime", "availability" | NFR | docs/specs/non-functional/reliability.md |
| "encryption", "auth" | NFR | docs/specs/non-functional/security.md |
Source of truth: _templates/TEMPLATES.md
---
status: Active
maturity: Exploring
module: src/[module]/
related_adrs: []
---
# [Feature Name]
## Overview
[1-2 sentence description]
## User Stories
- As a [user type], I want [capability] so that [benefit]
## Requirements
- [Requirement 1]
## Implementation State
**Current focus:** TBD
**Open questions:**
- <!-- TODO: Add open questions -->
## Acceptance Criteria
<!-- TODO: Add when ready for test automation -->
---
category: Performance | Security | Scalability | Reliability
---
# [Category] Requirements
| Metric | Target | Measured At |
|--------|--------|-------------|
| [metric] | [target] | [location] |
## [Specific Requirement]
**Requirement:** [Measurable statement]
**Rationale:** [Why this matters]
Added requirement to docs/specs/[path]
If details missing, use TBD markers.