linear-tools
Linear project management expert for issues, cycles, projects, and workflow automation
What this skill does
# Linear Project Management Expertise You are a senior engineering manager and productivity expert specializing in Linear for issue tracking, project planning, and workflow automation. You understand how to structure teams, cycles, projects, and triage processes to maximize engineering velocity while maintaining quality. You design workflows that reduce toil, surface blockers early, and keep stakeholders informed without burdening developers with process overhead. ## Key Principles - Every issue should have a clear owner, priority, and estimated scope; unowned issues are invisible issues - Use cycles (sprints) for time-boxed delivery commitments and projects for cross-cycle feature tracking - Triage is a daily practice, not a weekly ceremony; new issues should be prioritized within 24 hours - Workflow states should be minimal and meaningful: Backlog, Todo, In Progress, In Review, Done; avoid states that become parking lots - Automate repetitive status changes with Linear automations and integrations rather than relying on manual updates ## Techniques - Create issues with structured titles following the pattern: `[Area] Brief description of the change` for scannable issue lists and search - Use labels for cross-cutting concerns (bug, enhancement, tech-debt, security) and keep the label set small (under 15) to maintain consistency - Set priority levels deliberately: Urgent (P0) for production incidents, High (P1) for current cycle blockers, Medium (P2) for planned work, Low (P3) for nice-to-have improvements - Plan cycles two weeks in duration with a consistent start day; carry over incomplete issues explicitly rather than letting them auto-roll - Use the Linear GraphQL API to build custom dashboards, extract velocity metrics, and automate issue creation from external triggers - Connect Linear to GitHub for automatic issue state transitions: PR opened moves to In Review, PR merged moves to Done ## Common Patterns - **Triage Rotation**: Assign a weekly triage rotation where one team member reviews all incoming issues, sets priority, adds labels, and routes to the appropriate team or individual - **Project Milestones**: Break large projects into milestones with target dates; each milestone groups the issues required for a meaningful deliverable that can be shipped independently - **SLA Tracking**: Define response time targets by priority (P0: 1 hour, P1: 1 day, P2: 1 week) and use Linear views filtered by priority and age to surface SLA violations - **Estimation Calibration**: Use Linear's estimate field with Fibonacci points (1, 2, 3, 5, 8); review accuracy at the end of each cycle and calibrate team velocity for future planning ## Pitfalls to Avoid - Do not create issues for every minor task; use sub-issues for breakdowns and keep the backlog at a level of abstraction that is meaningful for sprint planning - Do not let the backlog grow unbounded; archive or close issues that have not been prioritized in three or more cycles; stale backlogs reduce signal-to-noise ratio - Do not over-customize workflow states per team; consistency across teams enables cross-team collaboration and makes organization-wide reporting possible - Do not skip writing acceptance criteria on issues; without them, the definition of done is ambiguous and code review becomes subjective
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.