Coordinate beta review rounds and merge validation for CDD development cycles.
npx skills add https://github.com/usurobor/cnos --skill beta-usurobor
Please help me install this Agent Skill. Skill: beta Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/beta Command: npx skills add https://github.com/usurobor/cnos --skill beta-usurobor
Maintains independent judgment across the beta development cycle by enforcing a coherent review, merge, and beta close-out process with auditable artifacts and clear ownership.
Load origin/cycle/{N} surfaces and initiate the first beta review based on the cycle's diff.
High-intent search queries and answers about installing and using this skill.
Beta cycle governance preserves independent judgment by enforcing structured review rounds, identity truth checks, and non-destructive merge validation before changes land. It prevents direct implementation or branch ownership during the cycle to maintain reviewer autonomy.
Pre-merge validation requires loading canonical surfaces like CDD.md and beta/SKILL.md to check readiness signals. You execute structured review rounds to verify identity truth, canonical freshness, and non-destructive merge testing before approving changes.
You produce beta close-out artifacts after completing round-based review governance and pre-merge validation. These artifacts finalize the beta phase and transfer control to gamma and delta roles according to the CDS lifecycle.
Yes, beta review specifically applies to CDD development cycles where beta reviewers assess changes. It engages directly with gamma and delta roles, satisfying governance checks for gamma artifact completeness and implementation-contract coherence.
No, beta role governance explicitly prevents environment-level branch ownership during a cycle. It enforces beta's independence and failure modes to ensure reviewers cannot directly implement changes, maintaining strict separation of duties.
Beta intake loads canonical surfaces including CDD.md, beta/SKILL.md, review/SKILL.md, and release/SKILL.md. These surfaces provide readiness signals required to initiate the first beta review based on the cycle's diff.
usuroborWrite gamma-clarification.md to a cycle branch to signal live-source re-reads.
usuroborSelect the next CDS cycle gap using canonical rule-based logic.
usuroborOrchestrate the α governance lifecycle and artifact close-out in CDD cycles.
chf3198Audit GitHub repository and organization rulesets and generate governance reports.
