Menu
Lightweight project requirements checklist surfaced via /brief. Use to track or update outstanding project tasks.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Strategic guidance from the advisor model on a question, with optional focus area and depth. Use before consequential decisions or to review a plan.
Session bootstrap — loads shared memories and team standards from the Mori server. Use at session start, or after a context compaction with --post-compact.
Bundle the canonical memory set into one structured Markdown document for external-LLM review, audit, or dashboard download.
Ranked full-text search and browse over the shared memory store. Use to recall past decisions, patterns, or project context.
Runs the dream pipeline that distils session events into durable memories. Use to flush undreamed events or check dream status.
Bootstraps the memory store from existing material (repos, PDFs, transcripts). Use to seed memory from a project or document.
| name | req |
| description | Lightweight project requirements checklist surfaced via /brief. Use to track or update outstanding project tasks. |
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.
/req — DashboardCall mori_advisor-memory_req() with no arguments. Shows all requirements grouped by project with status counts.
/req --project <name> — Filter by projectCall mori_advisor-memory_req(project="<name>"). Shows requirements tagged with project-<name>.
/req --project <name> --status <value> — Filter by project and statusCall 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:
req-<project>-<slugified-title> (kebab-case)["project-<name>", "status-pending", "pri-<priority>"] + "fr" or "nfr" if specifiedmori_advisor-memory_write(name="<name>", title="<title>", description="<desc>", type="requirement", tags=<tags>, body="<desc>")/req done <name> — Mark completemori_advisor-memory_read(name) to get current tagsstatus-* tag with status-donemori_advisor-memory_write(name=..., tags=<updated tags>, type="requirement") with the same name and updated tags/req block <name> [--reason "<text>"] — Mark blockedmori_advisor-memory_read(name)status-* to status-blockedmori_advisor-memory_write/req wip <name> — Mark in-progressstatus-* to status-in-progress, write back/req import <filepath> [--project <name>] — Bulk importRead the file from the given path, parse requirements, create each one.
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 |
Parse the raw input string:
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)| 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 |