ring:dev-feedback-loop

Automating development cycle metrics collection involves tracking prompts and outcomes across gated tasks to compute assertiveness scores and aggregate data for root-cause analysis. This Skill enforces guardrails like mandatory TodoWrite to ensure traceable, auditable cycles.

An assertiveness score is a computed metric used to evaluate prompt quality across agents during development cycles. It aggregates cycle data to drive root-cause analysis and generates improvement recommendations for documentation updates.

Enforcing guardrails for traceable development cycles requires mandatory TodoWrite execution, threshold alerts, and structured feedback. These mechanisms ensure that cycle metrics and outcomes remain auditable and drive actionable improvements.

Yes, threshold alerts and escalation paths can be integrated into gated development tasks. The Skill applies structured feedback across your workflow to ensure traceable improvements and trigger alerts when metrics fall below defined thresholds.

Closing the feedback loop for faster delivery requires structured measurement, assertiveness scoring, and improvement reporting. This approach aggregates cycle metrics to provide visibility into performance and drive evidence-based improvements.

Generated improvement recommendations and cycle reports are written to docs/feedbacks/cycle-{date}/. This structured directory path organizes aggregated metrics and root-cause analysis outputs for traceable documentation updates.