req
/req
Lightweight project requirements checklist surfaced via /brief. Use to track or update outstanding project tasks.
- Author
- fjwood69 ↗
- Repository
- mori ↗
- Licence
- AGPL-3.0
- Last repository change
- 03.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.10.2026, without references to retired models or APIs.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
What it does and when to use it
Lightweight project requirements checklist surfaced via /brief. Use to track or update outstanding project tasks.
Original author description
Lightweight project requirements checklist surfaced via /brief. Use to track or update outstanding project tasks.
How it works
- Modes
- Tag conventions
- Argument parsing
- Examples
SKILL.md preview
--- name: req description: Lightweight project requirements checklist surfaced via /brief. Use to track or update outstanding project tasks. --- # /req — Project Requirements and Delivery Tracking When the user runs `/req`, parse the arguments and call the `mori_advisor-memory_req` MCP tool, or perform CRUD operations on `type=requirement` memories. Do NOT search for files locally. All tool calls go through the MCP server. ## Modes ### `/req` — Dashboard Call `mori_advisor-memory_req()` with no arguments. Shows all requirements grouped by project with status counts. ### `/req --project <name>` — Filter by project Call `mori_advisor-memory_req(project="<name>")`. Shows requirements tagged with `project-<name>`. ### `/req --project <name> --status <value>` — Filter by project and status Call `mori_advisor-memory_req(project="<name>", status="<value>")`. Status values: `done`, `pending`, `in-progress`, `blocked`. ### `/req add "<title>" --project <name> [--desc "<desc>"] [--pri high|medium|low] [--fr|--nfr]` Create a new requirement memory: 1. Compute name as `req-<project>-<slugified-title>` (kebab-case) 2. Build tags: `["project-<name>", "status-pending", "pri-<priority>"]` + `"fr"` or `"nfr"` if specified 3. Call `mori_advisor-memory_write(name="<name>", title="<title>", description="<desc>", type="requirement", tags=<tags>, body="<desc>")` 4. Report the created memory name ### `/req done <name>` — Mark complete 1. Call `mori_advisor-memory_read(name)` to get current tags 2. Replace any existing `status-*` tag with `status-done` 3. Call `mori_advisor-memory_write(name=..., tags=<updated tags>, type="requirement")` with the same name and updated tags ### `/req block <name> [--reason "<text>"]` — Mark blocked 1. Read current memory via `mori_advisor-memory_read(name)` 2. Swap `status-*` to `status-blocked` 3. Append reason to body if provided 4. Write back via `mori_advisor-memory_write` ### `/req wip <name>` — Mark in-progress 1. Read, swap `status-*` to `status-in-progress`, write back ### `/req import <filepath> [--project <name>]` — Bulk import Read the file from the given path, parse requirements, create each one. ## Tag conventions Each requirement memory uses these tags: | Tag | Purpose | |---|---| | `project-<name>` | Associates with a project | | `status-pending` | Not started (default) | | `status-in-progress` | Being worked on | | `status-done` | Completed | | `status-blocked` | Blocked by external dependency | | `pri-high`, `pri-medium`, `pri-low` | Priority | | `fr` | Functional requirement | | `nfr` | Non-functional requirement | ## Argument parsing Parse the raw input string: - **First positional**: mode (`add`, `done`, `block`, `wip`, `import`) or empty for dashboard - `--project` / `-p`: Project name - `--status` / `-s`: Status filter (dashboard mode only) - `--desc`: Description text - `--pri`: Priority (`high`, `medium`, `low`, default `medium`) - `--fr` | `--nfr`: Requirement type flag - `--reason`: Reason (for `block` mode) ## Examples | Input | Effect | |---|---| | `/req` | Dashboard of all requirements | | `/req --project myapp` | View myapp requirements | | `/req --project mori --status done` | Completed Mori requirements | | `/req add "OAuth2 login" --project myapp --pri high --fr` | Create new FR | | `/req done req-myapp-oauth2-login` | Mark as done | | `/req block req-myapp-oauth2 --reason "Waiting on IAM"` | Block with reason | | `/req import ./specs.md --project myapp` | Bulk import from file |
Versions
The database has no other skills named req.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version c31b89304768 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100requirements-framework-usage
This skill should be used when the user asks about "using requirements framework", "how to configure requirements", "add requirement checklist", "customize requirements", "requirements not working", "bypass requirements", "satisfy requirements", or needs help with the… - 100req-board-card
在需求看板(req-board,http://127.0.0.1:8899)上为当前或指定项目创建需求卡。当用户说「帮我建卡」「记到需求看板」「建一张 xx 项目的需求卡」「把 xx 记录为暂缓/待办需求」,或要求把本项目讨论的方案、需求、待办登记到 req-board 时使用。 - 100make-req
Decompose a task, plan, roadmap, or feature description into a structured set of requirements grouped for independent planning. Use when user says "make req", "make requirements", "decompose requirements", "extract requirements", or wants to break down a task into what needs to be true. - 100dx-req-dod
Check Definition of Done and auto-fix gaps — PR, tasks, docs — then post a summary to ADO. Use for 'check DoD'. Not for fetching requirements (dx-req), child Tasks (dx-req-tasks) or pre-PR checks (dx-step-verify). - 100make-req
Decompose a task, plan, roadmap, or feature description into a structured set of requirements grouped for independent planning. Use when user says "make req", "make requirements", "decompose requirements", "extract requirements", or wants to break down a task into what needs to be true. - 100req-review
Review requirements docs for quality/completeness/consistency (IEEE 29148, ISO 25010, EARS); produce a gap list + fixes. Use when: review requirements, audit requirements, check requirements, requirements quality, are requirements complete, requirements analysis, requirements…