promotion-readiness-checklist

Name: promotion-readiness-checklist
Availability: InStock
Author: organvm-i-theoria

Assess repository readiness for governance state promotion with structured checklists and evidence requirements.

Updated May 16, 2026

Search Tags:#checklist #repository #governance #quality gates #promotion #state machine #readiness

Ready to run

npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill promotion-readiness-checklist-organvm-i-theoria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: promotion-readiness-checklist
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/promotion-readiness-checklist
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill promotion-readiness-checklist-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams managing multiple repositories lack a consistent, auditable way to decide when a repo is ready to move from one governance state to the next, leading to premature promotions, skipped quality gates, and missing evidence. ## Core Features & Use Cases - State Machine Enforcement: Defines the LOCAL → CANDIDATE → PUBLIC_PROCESS → GRADUATED → ARCHIVED lifecycle with a hard no-skip rule for every transition. - Structured Checklists: Provides per-transition requirement checklists covering seed.yaml, README, CI pipelines, test coverage thresholds, security reviews, and stranger tests. - Evidence Templates: Supplies markdown evidence blocks and a promotion request template so every decision leaves an auditable record. - Use Case: Before promoting a service from CANDIDATE to PUBLIC_PROCESS, run the assessment to verify CI pass rate, test coverage, linting, branch protection, and deployment history, then record the evidence for audit. ## Quick Start Ask the agent to assess whether this repository is ready for promotion from CANDIDATE to PUBLIC_PROCESS and produce the evidence record.

Frequently Asked Questions about promotion-readiness-checklist

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

FAQPage Schema

How do I assess if a repository is ready for promotion?▼

Run the promotion readiness assessment for the current and target governance state. The checklist verifies requirements like seed.yaml, CI pass rate, test coverage, and security review, then produces an evidence record documenting each check.

What are the governance states in a repository promotion lifecycle?▼

The lifecycle is LOCAL → CANDIDATE → PUBLIC_PROCESS → GRADUATED → ARCHIVED. Each transition has explicit requirements, and skipping states is prohibited to prevent quality gaps.

What evidence is required for a governance state transition?▼

Each transition requires a markdown evidence block recording concrete results: CI pass rates, test coverage percentages, linting status, security scan dates, and assessor identity. Checkmarks without supporting evidence are treated as an anti-pattern.

What test coverage is required for repository promotion?▼

CANDIDATE to PUBLIC_PROCESS requires a minimum of 30% coverage with 60% as the target. PUBLIC_PROCESS to GRADUATED raises the minimum to 60% with 80% as the target, alongside higher CI pass rate thresholds.

Can a repository skip a governance state during promotion?▼

No. The state machine enforces a hard no-skip rule: every transition requires explicit evidence of meeting all requirements for that stage. Skipping states is listed as an anti-pattern because shortcuts create governance gaps.