requirements-manager 0.1.1

Plain-text requirements management tool
Documentation
---
_version: '1'
uuid: 0a71da3b-3684-4d58-ba36-9b74fb2cec85
created: 2025-10-26T16:55:20.079234662Z
parents:
- uuid: b871f9b8-ae8f-405b-8727-11e2409f20c3
  fingerprint: 7f9c8e5d4b3a2f1e0d9c8b7a6f5e4d3c2b1a0f9e8d7c6b5a4f3e2d1c0b9a8f7e
  hrid: USR-007
---
# SYS-018 Listing Filters and Scopes

## Statement

The `req list` command shall support filters that limit results by structural, categorical, or textual criteria without requiring additional scripting.

## Rationale

Large projects routinely ask focused questions: “Show me the SYS requirements under USR-004”, “List everything owned by the security namespace”, or “Find requirements mentioning ‘latency’”. Native filters keep those workflows fast, repeatable, and reviewer-friendly.

## Scope

Filtering transforms the listing command from a static report into an investigative tool. The experience shall make it obvious how to focus by kind, namespace, tags, graph position, or free text while keeping the syntax memorable at the keyboard.

Full filter catalogue, composition rules, and discoverability aids are captured in [SPC-002](./SPC-002.md).

## Verification

- Users filter by kind, namespace, graph position, or content without creating a custom script.
- Filters can be combined so the result set respects every supplied constraint.
- Pagination and batching allow large repositories to remain manageable.