ring:managing-dev-cycle

Cycle Management

When to use

• User wants to check the status of a running development cycle
• User wants to cancel an active development cycle
• Invoked with mode=status or mode=cancel

Skip when

• No development cycle is active or was recently started
• User is asking about general project status (not cycle-specific)

Unified skill for managing development cycle state. Provides two modes: status (read-only inspection) and cancel (state mutation with confirmation).

Mode Selection

This skill provides two modes selected by the mode parameter:

Mode	Purpose
status	Read-only — display cycle metrics
cancel	Mutating — cancel the active cycle

If no mode is provided, default to status.

---

Shared: State File Discovery

Both modes read from the same state files. Check for an active cycle in this order:

1. docs/ring:running-dev-cycle/current-cycle.json
2. docs/ring:planning-backend-refactor/current-cycle.json

If neither file exists or both contain a terminal status (completed, cancelled), report that no cycle is active and exit with the appropriate "no cycle" message for the current mode.

---

Mode: Status

Display the current development cycle status.

Output

Displays:

• Current cycle ID and start time
• Current phase (if phases[] is present in state)
• Epics: total, completed, in progress, pending
• Current epic and gate being executed
• Assertiveness score (if epics completed)
• Elapsed time

Example Output

Development Cycle Status

Cycle ID: 2024-01-15-143000
Started: 2024-01-15 14:30:00
Status: in_progress
Phase: Phase 2 - Core flows

Epics:
  Completed: 2/5
  In Progress: 1/5 (Epic 2.3)
  Pending: 2/5

Current:
  Epic: Epic 2.3 - Implementar refresh token
  Gate 0→8→9 lean flow (ring:implementing-tasks)
  Iterations: 1

Metrics (completed epics):
  Average Assertiveness: 89%
  Total Duration: 1h 45m

State file: docs/ring:running-dev-cycle/current-cycle.json (or docs/ring:planning-backend-refactor/current-cycle.json)