cycle-plan

Analyze team velocity and capacity to generate a validated cycle plan.

142|19|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/joa23/linear-cli --skill cycle-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cycle-plan
Source: https://github.com/joa23/linear-cli/tree/main/internal/skills/cycle-plan
Command: npx skills add https://github.com/joa23/linear-cli --skill cycle-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning software development cycles is challenging without data-driven guidance. This skill helps teams optimize cycle scope by analyzing velocity history and capacity to produce balanced, achievable plans.

Core Features & Use Cases

  • Analyze historical velocity to estimate feasible cycle capacity.
  • Assess team capacity, PTO, and focus time to avoid overcommitment.
  • Generate recommended cycle scope considering dependencies and workload balance across members.

Quick Start

Plan the next cycle by analyzing velocity and capacity data to produce a ready-to-apply cycle plan.

Frequently Asked Questions about cycle-plan

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

FAQPage Schema
How do I plan a sprint using team velocity and capacity data?▼

To plan a sprint using team velocity and capacity data, you analyze historical velocity records, assess current team availability including PTO, and evaluate workload balance to generate a validated and achievable cycle scope.

What is velocity-driven cycle planning in software engineering?▼

Velocity-driven cycle planning is a data-driven method to optimize sprint scope by analyzing historical velocity trends and current team capacity, ensuring workload balancing and preventing overcommitment across development cycles.

How do I assess dependency risks during sprint planning?▼

You assess dependency risks during sprint planning by analyzing cross-team dependencies and workload balance alongside team capacity, ensuring that identified dependency bottlenecks are factored into the validated cycle plan.

Can I balance workload across team members based on historical velocity?▼

Yes, you can balance workload across team members by applying historical velocity analysis and current capacity assessment to generate a cycle plan that factors in individual focus time, PTO, and overall team availability.

Does cycle planning work for managing team capacity and PTO?▼

Yes, cycle planning works for managing team capacity by assessing individual PTO and focus time, applying these constraints against your historical velocity to avoid overcommitment and produce a balanced development cycle.

What is the best way to avoid overcommitment in sprint planning?▼

The best way to avoid overcommitment in sprint planning is to generate a recommended cycle scope by analyzing historical velocity, assessing team capacity constraints like PTO, and evaluating dependency risks across the team.