moscow
MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have. Use for scope definition, feature prioritization, or when everything feels equally important.
What this skill does
# MoSCoW Prioritization Categorize items into Must have, Should have, Could have, and Won't have for clear scope and priorities. ## Instructions Take the list of items provided and sort them into MoSCoW categories. Be rigorous about what's truly a "Must"—if the project/goal can still succeed without it, it's not a Must. ### Output Format **Context** What are we prioritizing for? What are the constraints (time, budget, capacity)? **Prioritized List** ### Must Have (Critical) *Without these, the project fails or is pointless* - [ ] [Item] — [Why it's a must] - [ ] [Item] — [Why it's a must] ### Should Have (Important) *Significantly adds value; painful to omit but project survives* - [ ] [Item] — [Value it adds] - [ ] [Item] — [Value it adds] ### Could Have (Nice to Have) *Desirable if time permits; low impact if cut* - [ ] [Item] — [Why it's optional] - [ ] [Item] — [Why it's optional] ### Won't Have (Not This Time) *Explicitly out of scope; may revisit later* - [ ] [Item] — [Why it's deferred] - [ ] [Item] — [Why it's deferred] **Effort Distribution** | Category | Items | Est. Effort % | |----------|-------|---------------| | Must | X | ≤60% | | Should | X | ~20% | | Could | X | ~10% | | Won't | X | 0% (deferred) | **Red Flags** - If Must > 60% of effort: scope may be too large - If no Won'ts: probably not being honest about constraints - If everything is Must: priorities haven't been set **Rationale** Explain the key trade-offs made and the reasoning behind contentious categorizations. **Next Step** What's the first Must item to tackle? ## Guidelines - Ask "If we shipped without this, would we fail?" for each Must - Challenge "Musts" that are really "someone really wants this" - Make Won'ts explicit—avoids scope creep later - Consider dependencies (a Must might require a "hidden" Must) - Stakeholder alignment is essential—this isn't just your opinion $ARGUMENTS
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.