rdr-create

Create structured Research-Design-Review documents with IDs and governance metadata.

4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Hellblazer/nexus --skill rdr-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rdr-create
Source: https://github.com/Hellblazer/nexus/tree/main/nx/skills/rdr-create
Command: npx skills add https://github.com/Hellblazer/nexus --skill rdr-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and manages structured Research-Design-Review documents to capture technical decisions.

Core Features & Use Cases

  • Bootstrap and organize an RDR directory resolved from the project config.
  • Assign a unique ID, bootstrap an RDR file with metadata, and record governance in memory.
  • Generate a living README index and ensure traceability for future work and audits.

Quick Start

Create an RDR by saying "create an RDR" or by triggering the /rdr-create command to start a new document.

Frequently Asked Questions about rdr-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a Research-Design-Review document and when do I need one?

A Research-Design-Review (RDR) document captures technical decisions for engineering governance. You need an RDR when you want to bootstrap structured decision documentation with traceable metadata, IDs, and an indexed README for audits.

How do I create a Research-Design-Review document for my engineering project?

To create a Research-Design-Review document, trigger the bootstrap workflow to assign a unique ID, generate a ready-to-use Markdown file with governance metadata, and automatically update a living README index for your project directory.

Can I use this to bootstrap an RDR directory without manual setup?

Yes, you can bootstrap an RDR directory automatically resolved from your project config. The workflow handles end-to-end setup including ID assignment, memory recording, and generating the indexed README without manual directory structuring.

What's the best way to maintain decision documentation and ensure traceability for audits?

The best way to maintain decision documentation is using a structured RDR workflow that records governance metadata in memory and generates a living README index, ensuring full traceability for future work and technical audits.

Do I need any dependencies to assign RDR IDs and record governance metadata?

No external dependencies are required to assign RDR IDs and record governance metadata. The workflow operates independently to bootstrap files, assign unique identifiers, and store memory records within your project structure.