cycle-plan

Analyze velocity and capacity to plan software development cycles.

Updated Apr 8, 2024
One-click install
npx skills add https://github.com/tumes/dotfiles-nvim --skill cycle-plan-tumes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cycle-plan
Source: https://github.com/tumes/dotfiles-nvim/tree/main/claude/skills/cycle-plan
Command: npx skills add https://github.com/tumes/dotfiles-nvim --skill cycle-plan-tumes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning software development cycles is time-consuming and error-prone without data-driven guidance.

Core Features & Use Cases

  • Velocity-based sprint planning: analyze historical velocity to forecast capacity.
  • Dependency-aware selection: respect task dependencies and balance workload.
  • Capacity validation: ensure planned work fits within available capacity and resources.

Quick Start

Run velocity and capacity analysis to draft the next sprint 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 sprints using historical velocity data?

Sprint planning using historical velocity analyzes past cycle throughput to forecast available capacity. This approach balances workload and validates that planned development tasks fit within projected resource limits.

What is the best way to manage task dependencies during sprint planning?

Dependency-aware sprint planning respects task relationships when selecting work items. It evaluates linked tasks to prevent scheduling conflicts and ensures workload balancing across the development cycle.

How does capacity validation work for software development cycles?

Capacity validation ensures planned work fits within available resources by comparing proposed tasks against calculated limits. It prevents overallocation by checking workload data against team capacity constraints.

Can I balance team workload when planning a development cycle?

Workload balancing distributes tasks across team members based on capacity analysis. It evaluates velocity data to equalize assignments and ensures no single resource is overburdened during the cycle.

Why does velocity-driven sprint planning fail to account for complex dependencies?

Velocity-driven planning focuses on throughput forecasting rather than dependency resolution. It must be paired with dependency-aware selection to accurately map task sequences and validate workload capacity constraints.