alpha

Orchestrate the α governance lifecycle and artifact close-out in CDD cycles.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill alpha-usurobor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alpha
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/alpha
Command: npx skills add https://github.com/usurobor/cnos --skill alpha-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

α governance and artifact closure in complex cycles can drift, leading to unclear accountability and untracked changes. This skill formalizes the cross-surface coordination, ensuring the α close-out and self-coherence traces are produced and maintained.

Core Features & Use Cases

  • Ensures disciplined self-coherence across the cycle, including gap definition, skill loading, AC mapping, and evidence collection.
  • Coordinates pre-review gating and beta review readiness to reduce rework.
  • Provides auditable artifacts and traceability for peer review and release processes.

Quick Start

Follow the α governance workflow to initialize cycle N, load required skills, and begin the self-coherence and review gate processes.

Frequently Asked Questions about alpha

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

FAQPage Schema
What is an alpha governance lifecycle and artifact close-out process?▼

It solves accountability drift and untracked changes in complex cycles by formalizing cross-surface coordination, ensuring self-coherence traces are produced, and generating traceable artifacts for peer review.

How do I automate cross-surface audits and self-coherence artifact generation?▼

Automate cross-surface audits and self-coherence artifacts by initializing a governance cycle, loading required skills, mapping acceptance criteria, and executing pre-review gate checks to collect traceable evidence.

Does the alpha close-out workflow satisfy pre-review gate requirements for peer review?▼

Yes, the alpha close-out workflow coordinates pre-review gating and beta review readiness. It enforces role constraints and produces traceable evidence to satisfy peer review gate requirements.

Can I use a governance workflow to coordinate gap definition and evidence collection across multiple peers?▼

Yes, you can use this governance workflow to coordinate gap definition, skill loading, acceptance criteria mapping, and evidence collection across multiple peers within complex design-to-close-out cycles.

What is the best way to ensure traceable evidence for beta review in a design cycle?▼

The best way to ensure traceable evidence for beta review is to enforce disciplined self-coherence across the cycle, coordinate pre-review gating, and generate auditable artifacts that satisfy the seven-axis implementation contract.

When should I not use a formalized alpha close-out process for artifact management?▼

Avoid a formalized alpha close-out process if your design workflows do not require cross-surface audits, multiple peer gate checks, or strict traceability evidence for beta review readiness.