using-nuclear-grade

Automate scoping and routing decisions for AI-assisted software changes.

33|Updated May 24, 2026
One-click install
npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill using-nuclear-grade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-nuclear-grade
Source: https://github.com/FlyFission/nuclear-grade-context-engineering/tree/main/skills/using-nuclear-grade
Command: npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill using-nuclear-grade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined, auditable starting point for any AI-assisted change by requiring explicit mode selection and a single fact before execution, then routing the work to the appropriate rigor and recording it for traceability.

Core Features & Use Cases

  • Enforces pre-action mode declaration (Quick or Standard-plus) before any tool call.
  • Creates and anchors a minimal change record that binds the change to a specific goal and risk profile.
  • Routes work to the corresponding skill cluster based on the chosen mode, ensuring controlled progression from proposal to release.
  • Maintains an auditable trail under .nuclear/changes/ for governance and review.

Quick Start

Before acting, declare the mode (Quick or Standard-plus) and the one fact that sets it, then generate the minimal change record and route the work to the correct skill cluster.

Frequently Asked Questions about using-nuclear-grade

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

FAQPage Schema
How do I create an auditable change record for AI-assisted code modifications?

To create an auditable change record for AI-assisted code modifications, declare a Quick or Standard-plus mode and a single anchoring fact before execution. The system then generates a minimal change record under `.nuclear/changes/` to bind the change to its goal and risk profile for governance.

What is mode declaration in AI-assisted change management workflows?

Mode declaration in AI-assisted change management workflows is the process of explicitly selecting a Quick or Standard-plus rigor level before any tool calls. It ensures controlled progression by routing work to the appropriate skill cluster based on the chosen mode and risk profile.

How do I route AI-assisted repository changes through different rigor levels?

You route AI-assisted repository changes by selecting either Quick or Standard-plus mode during the initial scoping phase. This choice routes the work to the corresponding skill cluster, ensuring controlled progression from proposal to release with the appropriate level of governance.

Does this approach to change management work for repo adoption and software releases?

Yes, this routing approach applies to repo adoption, code changes, and software releases. It automates initial scoping decisions to ensure auditable change records and proper routing through skill clusters for any AI-assisted modification.

When do I need to use a nuclear-grade routing process for software changes?

You need a nuclear-grade routing process when your AI-assisted software changes require strict governance, an audit trail, and traceable decision records. It is essential for maintaining disciplined, auditable progress from proposal to release.