ring:dev-feedback-loop

Analyze development cycle metrics and outcomes to identify improvement patterns.

4|Updated Jan 10, 2026

Search Tags:#metrics #learning #process-improvement #continuous-improvement #dev-cycle #gate-analysis #cycle-analytics

Ready to run

npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-dev-feedback-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ring:dev-feedback-loop
Source: https://github.com/LerianStudio/ring-for-opencode/tree/main/assets/skill/dev-feedback-loop
Command: npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-dev-feedback-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures metrics and learnings from completed development cycles to enable continuous improvement across teams and projects.

Core Features & Use Cases

Per-cycle and per-gate metrics: duration, iterations, compliance gaps, and issues across gates (Implementation, DevOps, SRE, Testing, Review, Validation).
Aggregate insights and learning categories: technical patterns and process patterns to guide future cycles.
State-aware analysis: reads ring:dev-cycle data (agent_outputs, metrics, and tasks gate_progress) to derive actionable recommendations.

Quick Start

Automatically analyze new development cycles when they complete, or run a manual analysis to review historical cycles. The analysis reads from ring:dev-cycle state files to extract metrics and outcomes.

Frequently Asked Questions about ring:dev-feedback-loop

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

FAQPage Schema

How do I analyze development cycle metrics to find improvement opportunities?▼

To analyze development cycle metrics, this Skill aggregates per-gate timings, iterations, and issues from completed cycles to identify technical and process patterns. It reads cycle data directly to extract actionable improvement recommendations.

What is gate analysis in a dev cycle?▼

Gate analysis in a dev cycle evaluates outcomes across specific stages like Implementation, DevOps, SRE, Testing, Review, and Validation. It captures duration, iterations, and compliance gaps per gate to summarize learning categories for future cycles.

How do I extract learning categories from completed development cycles?▼

You extract learning categories by applying state-aware analysis to ring:dev-cycle data, including agent outputs and metrics. The Skill processes this data to derive technical and process patterns that guide future development cycles.

Do I need specific state files to run cycle analytics?▼

Yes, you need ring:dev-cycle state files to run cycle analytics. The Skill requires access to cycle data, metrics, and agent outputs within these state files to extract per-gate timings, iterations, and issues for analysis.

Can I manually review historical cycle metrics and outcomes?▼

Yes, you can manually run an analysis to review historical cycle metrics and outcomes. The Skill reads from ring:dev-cycle state files to extract per-gate timings, iterations, and issues, aggregating insights across completed cycles.