Agent skill

Cycle Plan

by joa23 in joa23/linear-cli

Plan Linear cycles using velocity analytics. An agent skill from joa23/linear-cli.

MITAuto-check passedProduct & Project Management

Install Cycle Plan

skills CLI
$ npx skills add joa23/linear-cli --skill cycle-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install joa23/linear-cli cycle-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/joa23/linear-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cycle-plan .claude/skills/cycle-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cycle-plan
GitHub stars
144
Token cost
~1.2k tokens
SKILL.md length
228 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Plan Linear cycles using velocity analytics. An agent skill from joa23/linear-cli.

  • Works in 5 steps: Analyze Historical Velocity → Review Available Capacity → Get Issues for Planning → …
  • Product & Project Management work in your project
  • SKILL.md covers When to Use, Process, Velocity Analysis and Planning Output, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cycle Plan is an agent skill from joa23/linear-cli. Plan Linear cycles using velocity analytics. Suggests scope based on historical capacity, identifies dependency risks, balances workload.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. The repository describes itself as: A token-efficient CLI for Linear. The licence is MIT.

When your agent uses it

  • Product & Project Management work in your project

Example prompts

  • “/cycle-plan”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Analyze Historical Velocity
  2. Review Available Capacity
  3. Get Issues for Planning
  4. Select Issues for Cycle
  5. Validate Plan

What it can do on your machine

Read from SKILL.md and the folder at commit 575c6f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cycle Plan loads about 1.2k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 228 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from joa23/linear-cli at commit 575c6f0, republished under its MIT licence (© joa23). 228 words, ~1,164 tokens.

Download SKILL.mdSave it as .claude/skills/cycle-plan/SKILL.md (or your agent's skills folder).
name
cycle-plan
description
Plan Linear cycles using velocity analytics. Suggests scope based on historical capacity, identifies dependency risks, balances workload.

Cycle Plan Skill - Sprint Planning

You are an expert at planning software development cycles based on team velocity.

When to Use

Use this skill when:

  • Planning the next sprint/cycle
  • Deciding what to include in a cycle
  • Balancing workload across team members

Process

CRITICAL: Setup First

ALWAYS check if .linear.yaml exists. If not, run:

bash
linear init  # Select default team - REQUIRED for cycle operations
  1. Analyze Historical Velocity

    bash
    linear cycles analyze --team ENG --count 10 --format full

    Parse the JSON to extract velocity metrics, completion rates, and recommendations.

  2. Review Available Capacity

    • Check team size
    • Account for PTO/holidays
    • Consider focus time needs
    • Use P20/P50/P80 recommendations from analyze command
  3. Get Issues for Planning

    bash
    # Get backlog issues (returns ALL issues, not just assigned)
    linear issues list --state Backlog --format full --limit 100
    
    # Get current cycle issues
    linear issues list --cycle current --format full
    
    # Get next cycle issues (if already planned)
    linear issues list --cycle next --format full
  4. Select Issues for Cycle

    • Start with P1/P2 issues (--priority 1 or --priority 2)
    • Respect dependencies (use linear deps --team ENG)
    • Balance across team members
    • Stay within recommended capacity
  5. Validate Plan

    • Total estimates <= capacity
    • No cross-cycle blockers
    • Even distribution

Velocity Analysis

The linear cycles analyze command provides:

VELOCITY ANALYSIS: Team ENG (5 cycles)
════════════════════════════════════════
Average Velocity: 34 points/cycle
Completion Rate: 85%
Scope Creep: 12%

CYCLE HISTORY
────────────────────────────────────────
Cycle 23: 38 pts (92% complete)
Cycle 22: 32 pts (88% complete)
Cycle 21: 35 pts (82% complete)
Cycle 20: 28 pts (78% complete)
Cycle 19: 37 pts (90% complete)

RECOMMENDATION
────────────────────────────────────────
Target: 32-36 points for next cycle
Buffer: Reserve 10% for unplanned work

Planning Output

CYCLE PLAN: Sprint 24
════════════════════════════════════════
Capacity: 40 points (4 engineers)
Target: 36 points (90% capacity)
Buffer: 4 points for unplanned work

PLANNED ISSUES
────────────────────────────────────────
ENG-201 [P1] Auth refactor      8pts @alice
ENG-202 [P1] Payment fix        5pts @bob
ENG-203 [P2] Dashboard update   8pts @carol
ENG-204 [P2] API optimization   5pts @dave
ENG-205 [P3] Docs update        3pts @alice
ENG-206 [P3] Test coverage      5pts @bob
────────────────────────────────────────
Total: 34 points

WORKLOAD BALANCE
────────────────────────────────────────
@alice: 11 pts (28%)
@bob:   10 pts (25%)
@carol: 8 pts (20%)
@dave:  5 pts (13%)
Unassigned: 0 pts

DEPENDENCY RISKS
────────────────────────────────────────
ENG-203 blocked by ENG-201 (same cycle - OK)

Commands Used

bash
# FIRST: Ensure team context is set
linear init  # If .linear.yaml doesn't exist

# Analyze velocity (ALWAYS do this first)
linear cycles analyze --team ENG --count 10 --format full

# Get backlog issues for planning (returns ALL issues, not just assigned)
linear issues list --state Backlog --format full --limit 100

# Get high priority issues
linear issues list --priority 1 --format full

# Get issues by cycle
linear issues list --cycle current --format full
linear issues list --cycle next --format full
linear issues list --cycle 65 --format full  # Specific cycle number

# Filter by multiple criteria
linear issues list --state Backlog --priority 1 --labels customer --format full

# Check dependencies
linear deps --team ENG

# Assign to cycle
linear issues update ENG-201 --cycle current
linear issues update ENG-202 --cycle next
linear issues update ENG-203 --cycle 65  # Specific cycle number

Key Learnings

  • linear issues list returns ALL issues (not just assigned to you)
  • Use --format full for parsing output in scripts
  • Cycle numbers require team context from linear init
  • Always run linear cycles analyze before planning to understand capacity
  • Use filters to narrow results: --state, --priority, --labels, --cycle, --assignee

Best Practices

  1. Leave buffer - Plan to 80-90% capacity
  2. Front-load blockers - Schedule blocking issues early
  3. Balance workload - Distribute evenly across team
  4. Avoid cross-cycle deps - Don't plan work blocked by next cycle

© joa23, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/cycle-plan of joa23/linear-cli.

Open the folder on GitHubat commit 575c6f0

Compare with similar skills

Cycle Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cycle Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cycle Plan this skilljoa23/linear-cli144—~1.2kAutomated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed
  • A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes
  • Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from joa23/linear-cli

All 8 skills in this repo
  • Triage

    joa23/linear-cli

    Triage and prioritize Linear backlog issues using the linear CLI.

    144 GitHub stars~699 tokensUpdated 24 days ago
    Auto-check passed
  • Deps

    joa23/linear-cli

    Visualize and analyze issue dependencies in Linear. An agent skill from joa23/linear-cli.

    144 GitHub starsUsed in 1 repo~914 tokens
    Auto-check passed
  • Prd

    joa23/linear-cli

    Create agent-friendly Linear tickets with PRDs, sub-issues, and clear success criteria.

    144 GitHub stars~621 tokensUpdated 24 days ago
    Auto-check passed
  • Retro

    joa23/linear-cli

    Analyze completed Linear cycles for retrospectives. An agent skill from joa23/linear-cli.

    144 GitHub starsUsed in 1 repo~790 tokens
    Auto-check passed
  • Link Deps

    joa23/linear-cli

    Discover and link related issues as dependencies. An agent skill from joa23/linear-cli.

    144 GitHub stars~2.3k tokensUpdated 24 days ago
    Auto-check passed
  • Release

    joa23/linear-cli

    Pre-release checklist to ensure CHANGELOG, version numbers, tests, and documentation are updated before cutting a release.

    144 GitHub stars~3.2k tokensUpdated 24 days ago
    Auto-check passed

Questions about Cycle Plan

What does Cycle Plan do?

Plan Linear cycles using velocity analytics. An agent skill from joa23/linear-cli. Cycle Plan is an agent skill from joa23/linear-cli. Plan Linear cycles using velocity analytics.

When should I use Cycle Plan?

Cycle Plan fits situations like: product & Project Management work in your project.

How do I install Cycle Plan in Claude Code?

Run `npx skills add joa23/linear-cli --skill cycle-plan -a claude-code`. Or copy the skill folder (.claude/skills/cycle-plan in joa23/linear-cli) into .claude/skills/cycle-plan in your project. Claude Code loads it when a task matches its description.

How do I install Cycle Plan in Codex?

Run `npx skills add joa23/linear-cli --skill cycle-plan -a codex`. Or copy the skill folder (.claude/skills/cycle-plan in joa23/linear-cli) into .agents/skills/cycle-plan in your project. Codex loads it when a task matches its description.

Can I use Cycle Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add joa23/linear-cli --skill cycle-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cycle-plan, .gemini/skills/cycle-plan, .github/skills/cycle-plan and .opencode/skills/cycle-plan in your project.

What does Cycle Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Cycle Plan is instructions for the agent only.

Does Cycle Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cycle Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cycle Plan use?

Cycle Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cycle Plan use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cycle Plan?

Skills that share tags, products or a category with Cycle Plan: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cycle Plan?

joa23 (a GitHub user) maintains it in joa23/linear-cli, which has 144 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 13, 2026.

Source: joa23/linear-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.