rdr-close

Close an RDR with post-mortem, bead decomposition, and T3 archival metadata.

4|Updated Feb 21, 2026

Search Tags:#documentation #beads #post-mortem #archival #rdr #rdr-close

Ready to run

npx skills add https://github.com/Hellblazer/nexus --skill rdr-close

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rdr-close
Source: https://github.com/Hellblazer/nexus/tree/main/nx/skills/rdr-close
Command: npx skills add https://github.com/Hellblazer/nexus --skill rdr-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to formally close an RDR by capturing a post-mortem, decomposing the implementation plan into beads, and archiving the results to the knowledge store, ensuring traceability and reuse.

Core Features & Use Cases

Close an active RDR when implementation completes, with optional post-mortem creation and bead decomposition.
Create epic and task beads from the Implementation Plan, wire dependencies, and update archival state.
Regenerate the RDR README index and update semantic index to reflect closure.

Quick Start

Run the rdr-close flow to finalize an RDR, generate beads, and archive the post-mortem as needed.

Frequently Asked Questions about rdr-close

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

FAQPage Schema

How do I close an RDR and create a post-mortem after implementation?▼

Closing an RDR involves capturing optional post-mortem documentation, decomposing the implementation plan into epic and task beads, wiring dependencies, and updating the T3 archival metadata to ensure traceability and reuse.

What is bead decomposition in RDR archival?▼

Bead decomposition is the process of breaking down a completed implementation plan into epic and task beads, wiring their dependencies, and updating the archival state to preserve project structure within the knowledge store.

When do I need to update T2 close metadata and regenerate the RDR README?▼

You need to update T2 close metadata and regenerate the RDR README when an RDR completes implementation and requires formal closure, documentation updates, and semantic index updates to reflect the final archival state.

Can I archive post-mortem documentation without generating task beads?▼

Yes, creating a post-mortem and bead decomposition are optional steps during RDR closure. You can choose to archive post-mortem documentation independently while still satisfying the T2 close metadata and README regeneration requirements.

Does closing an RDR automatically update the semantic index?▼

Yes, closing an RDR automatically regenerates the RDR README index and updates the semantic index to reflect the closure. This ensures the knowledge store accurately tracks the finalized archival state and T3 metadata.