Is the 85% test coverage threshold configurable?

The 85% threshold is a hard gate within the Ring standards to ensure industry-standard code quality and minimize regression risks in AI-generated code.

Can I skip gates for simple tasks or hotfixes?

No. The dev-cycle skill operates on the principle that 'simple is not risk-free.' All 6 gates must be executed to prevent regression and maintain documentation standards, regardless of task size.

Why does Gate 4 require three different reviewers?

To ensure comprehensive quality, the system runs code, business logic, and security reviews in parallel. All three must pass to ensure the implementation is sound from every critical angle.

What happens if a task gets interrupted?

The skill maintains state in a local JSON file. You can use the --resume flag to pick up exactly where the cycle left off, preserving completed gate statuses.

Dev Cycle Orchestrator

Name: Dev Cycle Orchestrator
Author: LerianStudio

byLerianStudio

•

Deployment & DevOps

Orchestrates a mandatory 6-gate development workflow to ensure software engineering best practices and quality checkpoints for AI agents.

About

The Dev Cycle Orchestrator is the core engine of the Ring workflow system, designed to move development tasks through six rigorous quality gates: implementation, devops, SRE, testing, review, and validation. It prevents 'incremental compromise' by enforcing strict sequential execution, requiring TDD patterns, 85% test coverage, and a mandatory three-reviewer consensus. By coordinating specialized agents rather than performing manual edits itself, this skill ensures that every piece of code meets production-grade standards before final acceptance.

Key Features

Mandatory three-perspective code review system
17 GitHub stars
Six-gate quality enforcement (TDD to Validation)
State persistence with resume capability for long-running tasks
Specialized agent dispatch for role-based task execution
Automated metrics collection and severity-based blocker reporting

Use Cases

Executing complex feature development from PM-defined task files
Enforcing standardized observability and infrastructure patterns across a codebase
Maintaining strict TDD and testing thresholds in AI-driven development

About

Key Features

Mandatory three-perspective code review system
17 GitHub stars
Six-gate quality enforcement (TDD to Validation)
State persistence with resume capability for long-running tasks
Specialized agent dispatch for role-based task execution
Automated metrics collection and severity-based blocker reporting

Use Cases

Executing complex feature development from PM-defined task files
Enforcing standardized observability and infrastructure patterns across a codebase
Maintaining strict TDD and testing thresholds in AI-driven development