cycle-check

Compile weekly milestone progress, blockers, and next steps into a report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill cycle-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cycle-check
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/cycle-check
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill cycle-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly planning ritual to review progress, upcoming work, and blockers across the active milestone.

Core Features & Use Cases

  • Milestone progress snapshot: summarizes completed vs open issues and due dates.
  • Blocker detection and aging issues: surfaces blockers to inform decisions.
  • Auto-detection of current milestone: derives the active milestone from docs/IMPLEMENTATION_PLAN.md when no argument is provided.

Quick Start

Run /cycle-check to generate the current active milestone cycle report.

Frequently Asked Questions about cycle-check

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

FAQPage Schema
How do I automate weekly milestone reviews for GitHub issues and PRs?▼

Automate weekly milestone reviews by running a command that compiles progress, blockers, and next steps into a concise report. It queries GitHub CLI for active issues and PRs, summarizing completion status and flagging aging blockers.

What is a cycle check and how does it detect the active project milestone?▼

A cycle check is an automated planning ritual that reviews milestone progress. It auto-detects the active milestone by parsing docs/IMPLEMENTATION_PLAN.md when no milestone argument is provided during execution.

Can I use GitHub CLI to surface blockers and aging issues in my project report?▼

Yes, GitHub CLI queries are used to surface blockers and aging issues. The cycle check workflow flags these blockers to inform planning decisions and includes them in a structured weekly report.

How do I generate a progress snapshot for completed versus open issues?▼

Generate a progress snapshot by running the cycle check command. It summarizes completed versus open issues and due dates, producing a structured report of the active software project milestone.

Do I need an IMPLEMENTATION_PLAN.md file to run the weekly milestone report?▼

An IMPLEMENTATION_PLAN.md file is required for auto-detection of the current milestone. Without it, you must provide a milestone argument explicitly to generate the weekly progress report.

What's the best way to clear blockers fast during weekly project planning?▼

Clear blockers fast by automating the weekly planning ritual with a cycle check. It surfaces blockers and aging issues early, enabling quick decisions and highlighting upcoming work across multiple issues and PRs.