creating-change-records

Automate creation and revision of Nuclear-grade change records with traceability.

33|Updated May 24, 2026

Search Tags:#automation #workflow #templates #validation #traceability #evidence-based #change-record

Ready to run

npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill creating-change-records

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: creating-change-records
Source: https://github.com/FlyFission/nuclear-grade-context-engineering/tree/main/skills/creating-change-records
Command: npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill creating-change-records

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to create and maintain Nuclear-grade change records, ensuring complete traceability of scope, plan, evidence, and release decisions.

Core Features & Use Cases

Template-driven scaffolding for Quick or Standard records, with mandatory files and linked evidence.
Validation and linking of risk, plan, trace, and verification components to ensure a review-ready record.
Lifecycle support for starting new records or revising existing ones, with clear next actions and escalation guidance.

Quick Start

Start a new change-record by initiating the Quick or Standard workflow for your slug.

Frequently Asked Questions about creating-change-records

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

FAQPage Schema

How do I automate change-record creation with traceability and validation?▼

Automate change-record creation by using template-driven scaffolding to generate Quick or Standard records, validating required files, linked evidence, and exit criteria to ensure complete traceability and review readiness.

What is a Nuclear-grade change record and when do I need it?▼

A Nuclear-grade change record is a structured document ensuring complete traceability of scope, plan, evidence, and release decisions. You need it when maintaining strict evidence-based validation for high-stakes software changes.

Does this change-record workflow support both Quick and Standard modes?▼

Yes, the change-record workflow supports both Quick and Standard modes. It uses template-driven scaffolding to automate creation while enforcing mandatory files, linked evidence, and plain status labels for either mode.

How to validate exit criteria and source-lineage notes in a change record?▼

Validate exit criteria and source-lineage notes by applying the workflow's built-in validators, which check that required files, links, and evidence are present and verifiable within the change record.

When should I use Standard mode instead of Quick mode for change records?▼

Use Standard mode for change records when you need comprehensive template-driven scaffolding with full validation of risk, plan, trace, and verification components. Quick mode suits faster record creation with fewer mandatory components.

Why are plain status labels required in change-record validation?▼

Plain status labels are required in change-record validation to ensure records are verifiable and review-ready. They provide clear, unambiguous tracking of lifecycle states and next actions throughout the evidence-based workflow.