菜单
Plan Linear cycles using velocity analytics. Suggests scope based on historical capacity, identifies dependency risks, balances workload.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Triage and prioritize Linear backlog issues using the linear CLI. Analyzes staleness, blockers, dependency health, and priority mismatches. Use when the user asks about backlog grooming, sprint planning, issue prioritization, managing stale tickets, or cleaning up Linear issues.
Pre-release checklist to ensure CHANGELOG, version numbers, tests, and documentation are updated before cutting a release.
Visualize and analyze issue dependencies in Linear. Finds blocking chains, circular dependencies, and critical path items.
Discover and link related issues as dependencies. Searches for issues that should be connected and recommends dependency relationships to establish proper work order.
Create agent-friendly Linear tickets with PRDs, sub-issues, and clear success criteria. Use when planning features or breaking down work for agentic coding.
Triage and prioritize Linear backlog. Analyzes issues for staleness, blockers, and suggests priorities based on dependencies and capacity.
| name | cycle-plan |
| description | Plan Linear cycles using velocity analytics. Suggests scope based on historical capacity, identifies dependency risks, balances workload. |
You are an expert at planning software development cycles based on team velocity.
Use this skill when:
Analyze Historical Velocity
linear cycles analyze --team ENG --count 5
Review Available Capacity
Select Issues for Cycle
Validate Plan
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
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)
# Analyze velocity
linear cycles analyze --team ENG --count 5
# List upcoming issues
linear issues list --team ENG
# Check dependencies
linear deps --team ENG
# Assign to cycle
linear issues update ENG-201 --cycle current
linear issues update ENG-202 --cycle next