teamcraft:pick-next-issue
Show the highest-priority work items from the backlog and help the developer pick one to work on next. Use when the user says 'pick next issue', 'what should I work on next from the backlog', 'show me the backlog', 'what's highest priority in the backlog', or 'pick an issue for me'.
What this skill does
## Goal Help the developer pick their next piece of work from the backlog. Read the work item index, show what's available, and let them choose. ## What to Do **1. Read the backlog.** Read `.teamcraft/work/INDEX.md` to see all work items and their current status. If the index doesn't exist or is empty, tell the developer there are no work items tracked yet and point them to `/create-issue`. **2. Read individual work item files to resolve blockers.** For items in `backlog` or `ready` status, also read the work item file to extract any `relationships.blocked_by`. An item is "blocked" when any of its blockers is still in an active status (`backlog`, `ready`, `in-progress`, `in-review`) — not yet `done`. Picking blocked work is almost always wrong, so this is worth the extra reads. **3. Show available items.** Present work items that are in `backlog` or `ready` status, ordered by priority (critical > high > medium > low). For each item, show the ID, priority, effort (if set), and the one-line summary. Separate them into two groups: - **Ready to pick** — items with no open blockers. - **Blocked** — items with at least one blocker still open. Show the blocker IDs and their current status, so the developer knows what's holding each up. Don't hide them entirely — sometimes the developer realizes the blocker is wrong, or wants to pick up the blocker itself first. If there are items in `in-progress` status, mention them — the developer may have forgotten about work already started. **4. Let the developer choose.** The developer picks one (or decides none of the current items are right). If they pick a blocked item, gently note that it's blocked and ask if they want to proceed anyway, pick the blocker first, or pick something else. Don't refuse — the developer may have context you don't. If they pick an unblocked item, point them to `/plan-and-implement-issue <id>` to start working on it. ## Constraints - This skill is read-only. It does not change work item status — that's `plan-and-implement-issue`'s job when work actually starts. - If the developer wants more detail about a specific item before choosing, read the full work item file from `.teamcraft/work/<id>.md` and present it. - Don't recommend or pressure. Present the options and let the developer decide. They know their context better than you do. - Resolve blockers by reading each referenced ID's file and checking its `status`. If a referenced ID doesn't exist on disk, treat it as an open blocker but flag it as a probable stale reference — the developer should clean up the relationship.
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.