pickup-work
Picks up the next actionable Linear issue for the product represented by the current repository. Use when the user says "/pickup-work", "pickup work", "pick up an issue", "what should I work on next", or asks to start Linear work from a repo. Use when a local monorepo should be mapped to its Linear product initiative or project before assigning and starting an issue.
What this skill does
# Pickup Work Use this skill to choose and reserve the next Linear issue for the product represented by the current working directory. ## Workflow 1. Run `bun plugins/linear-planner/skills/pickup-work/scripts/detect-linear-context.ts` from the skills repo, passing the user's current working directory as the first argument when needed. 2. Read the JSON evidence: git root, repo name, remote names, detected Linear URLs, issue IDs, project hints, and initiative/product terms. 3. Search Linear using the strongest product candidates first. Prefer initiative and project matches over loose issue-title matches. 4. Fetch the most likely project or initiative, then list candidate issues for that project. If only an initiative is found, search/list issues across its product terms and linked projects. 5. Prefer issues that are unassigned or assigned to `me`, not blocked, not archived, not completed, and in Todo/Backlog/Suggestion-ready states. Exclude planning-template work unless the repo itself is the planner plugin. 6. Rank candidates by priority first, then whether the issue is already in the current cycle, then clarity of acceptance criteria, then recency. 7. Before mutating Linear, confirm the candidate is not blocked by open issues. If the tool output is ambiguous, fetch the issue and its blockers. 8. Assign the selected issue to `me` and move it to the team's best in-progress state. Use `Started`, `In Progress`, or the closest available in-progress status from the team status list. 9. Report the issue identifier, title, project, status change, selection rationale, and first concrete implementation step. ## Fallbacks - If no confident product match exists, summarize the local evidence and ask for the Linear project or initiative. - If no actionable issue exists, say which project was searched and list the reason each close candidate was skipped. - If Linear update fails, report the selected issue and the failed mutation separately so the user can retry or update it manually. ## Field rules - Treat Linear as the source of truth for assignment and workflow state. - Do not create new issues from this workflow. - Do not pick completed, canceled, duplicate, archived, blocked, or dependency-only issues. - Do not change labels, estimates, due dates, cycles, descriptions, projects, or milestones. - Do not assign a different person unless the user explicitly asks.
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.