rcode-incident-record

What problem does it solve?

This Skill turns resolved incidents and planned changes into durable documentation so teams do not lose critical context in Slack threads or meeting notes.

Core Features & Use Cases

• Change Records: Captures deploys, schema changes, infra changes, and other notable work in a consistent rcode template.
• Post-Mortems: Produces incident write-ups with timeline, root cause, contributing factors, action items, and Memory Bank updates.
• Memory Bank Hygiene: Updates known issues and decisions so the project’s institutional memory stays accurate after fixes ship.
• Use Case: A production hotfix caused downtime, and you need a clear incident report plus a linked change record for future review.

Quick Start

Ask the skill to document a resolved incident or completed change and save the result in the appropriate rcode Memory Bank path.