alienfast/cycle-plan
skills/cycle-plan/SKILL.md
Plan Linear cycles using velocity analytics. Suggests scope based on historical capacity, identifies dependency risks, balances workload.
testing
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add alienfast/claude cycle-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 6:08 PM4.6s1 file scanned
SKILL.md
- 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
-
Analyze Historical Velocity
linear cycles analyze --team ENG --count 5 -
Review Available Capacity
- Check team size
- Account for PTO/holidays
- Consider focus time needs
-
Select Issues for Cycle
- Start with P1/P2 issues
- Respect dependencies
- Balance across team members
-
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
# 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
Best Practices
- Leave buffer - Plan to 80-90% capacity
- Front-load blockers - Schedule blocking issues early
- Balance workload - Distribute evenly across team
- Avoid cross-cycle deps - Don't plan work blocked by next cycle
Related Skills
alienfast/full
testing
VerifiedTrustedCommunity
End-to-end Linear issue macro — runs /start then /finish in sequence, gated on the /quality-review verdict. Worktree mode is opt-in via the `wt` token, mirroring /start. Pauses only for plan approval and the deferred-items filing decision; otherwise autonomous. Use when the user says 'full PL-XX', 'ship PL-XX end-to-end', or invokes /full.
SKILL.mdUpdated May 28, 2026
alienfast/quality-review
development
VerifiedTrustedCommunity
Adversarial implementation review with triage and fix loop. Hard-gates on `pnpm check`, delegates to the quality-reviewer agent for categorized findings (Critical/High/Medium/Nice-to-Have/Approved), then triages and fixes findings via the developer agent. Loops until a re-review surfaces no new Critical/High/Medium findings (convergence), with a soft ceiling of 5 cycles before asking the user how to proceed; option 3 of that prompt terminates with verdict `escalated-to-architect`. Use when the user says 'review my work', 'check this implementation', 'adversarial review', 'quality review', or invokes /quality-review.
SKILL.mdUpdated Apr 29, 2026
alienfast/triage
testing
VerifiedTrustedCommunity
Triage and prioritize Linear backlog. Analyzes issues for staleness, blockers, and suggests priorities based on dependencies and capacity.
SKILL.mdUpdated Apr 15, 2026
alienfast/start
testing
VerifiedTrustedCommunity
Start working on a Linear issue — check blockers, assign, move to In Progress, create branch, plan implementation, execute with checkpoint updates, review and triage findings. Use when the user says 'start issue', 'work on PL-XX', 'begin PL-XX', or invokes /start.
SKILL.mdUpdated Apr 15, 2026