From nx
Use when needing to see all RDRs in the project with their status, type, and priority
npx claudepluginhub hellblazer/nexus --plugin nxThis skill uses the workspace's default tool permissions.
- User says "list RDRs", "show RDRs", "what RDRs exist"
Lists blueprint documents (ADRs, PRDs, PRPs) from docs/ directories with metadata like title, status, date extracted from YAML frontmatter and headers. Outputs markdown tables for audits or indexes.
Displays Plan-Build-Run project status dashboard, progress, blockers from .planning files, and suggests next actions.
Share bugs, ideas, or general feedback.
/nx:rdr-listAll data is pre-loaded in the command context. Do NOT make additional Bash, Read, or tool calls — the /nx:rdr-list command already gathered:
.nexus.yml or default docs/rdr){repo}_rdr projectYour job is to format and filter the pre-gathered data.
| File | Title | Status | Type | Priority |
|------|-------|--------|------|----------|
| RDR-001-project-structure.md | Project Structure | Recommendation | Architecture | High |
| RDR-002-qdrant-server-setup.md | Qdrant Server Setup | Final | Infrastructure | Medium |
Apply filters if specified in $ARGUMENTS:
--status=draft — only show rows where Status matches (case-insensitive)--type=feature — only show rows where Type matches--has-assumptions — only show RDRs that have T2 records in contextEmit drift warnings if:
--status, --type, or --has-assumptionsRDR-NNN-name.md naming (Arcaneum style) or NNN-name.md or other conventions — the command handles all patterns.---) or a ## Metadata section with - **Key**: Value lines — both are parsed by the command.