choosing-what-to-control
CommunityDefine and lock the approved state of changes.
Software Engineering#ownership#audit#evidence#control#risk#configuration-management#change-management
AuthorFlyFission
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Keeps track of which changes across code, prompts, models, tools, dependencies, docs, tests, evals, releases, or claims require an approved state, preventing drift and untracked power.
Core Features & Use Cases
- Identifies all change-worthy items that affect trust, release readiness, or repeatability.
- Records owner, current state, intended state, evidence links, and re-check triggers to maintain auditable change histories.
- Produces the controlled-items.md and supports escalation when drift occurs.
Quick Start
List items that must remain under control for this change and specify each item's owner, current state, intended state, and re-check trigger.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: choosing-what-to-control Download link: https://github.com/FlyFission/nuclear-grade-context-engineering/archive/main.zip#choosing-what-to-control Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 510,000+ vetted skills library on demand.