linear-sprint
Sprint planning and analytics - status, progress, burndown, velocity, carry-over. Use when managing sprints.
Works with
--- name: linear-sprint description: Sprint planning and analytics - status, progress, burndown, velocity, carry-over. Use when managing sprints. license: MIT --- # Sprint Planning ```bash # Current sprint status linear-cli sp status -t ENG # Sprint progress (completion bar) linear-cli sp progress -t ENG # Plan next sprint (view planned issues) linear-cli sp plan -t ENG # Carry over incomplete issues to next cycle linear-cli sp carry-over -t ENG --force # ASCII burndown chart linear-cli sp burndown -t ENG # Velocity across recent sprints linear-cli sp velocity -t ENG linear-cli sp velocity -t ENG --cycles 10 # Last 10 sprints linear-cli sp velocity -t ENG --output json ``` ## Subcommands | Command | Purpose | |---------|---------| | `status` | Current sprint overview | | `progress` | Visual completion bar | | `plan` | Next cycle's planned issues | | `carry-over` | Move incomplete to next cycle | | `burndown` | ASCII burndown chart | | `velocity` | Sprint velocity + trend analysis | ## Flags | Flag | Purpose | |------|---------| | `-t TEAM` | Team key (required) | | `--cycles N` | Number of past cycles for velocity | | `--force` | Skip carry-over confirmation | | `--output json` | JSON output | ## Exit Codes `0`=Success, `1`=Error, `2`=Not found, `3`=Auth error
More Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

