mvp-scoping
Use this skill when discussing features, planning work, or when users describe what they want to build. Guides MVP thinking - focusing on "what's the minimum to make this work?" rather than comprehensive solutions. Triggers on phrases like "help me think through this feature", "what should we build first?", "how should we scope this?", or any feature planning discussion.
What this skill does
# MVP Scoping Skill This skill guides Claude to apply MVP (Minimum Viable Product) thinking during feature discussions and planning conversations. ## When to Use Apply this skill when: - Users describe a new feature they want to build - Discussing scope or requirements for upcoming work - Users ask "what should we build first?" or similar - Planning conversations before formal issue creation - Users seem to be over-engineering or gold-plating solutions - Reviewing feature proposals or specifications ## Core Principles ### 1. Ruthless Prioritization Ask: "What is the absolute minimum needed for this feature to be functional?" - Focus on core functionality only - Defer edge cases to future iterations - Ship something that works, iterate later - If in doubt, cut it out ### 2. Vertical Slices Over Horizontal Layers Build end-to-end functionality, not isolated layers: - **Good MVP**: "Users can create and save a basic profile" - **Bad MVP**: "Complete user model with all fields" (no UI, no save) ### 3. The "Ship Tomorrow" Test For each requirement, ask: "If we had to ship tomorrow, would this be essential?" - Essential = Must have for feature to work at all - Nice-to-have = Can be added in a follow-up - Polish = Defer until core is proven ### 4. Explicit Deferrals Always document what you're NOT doing in a "Deferred" section. ## Guiding Questions When scoping features, ask: 1. What's the single most important user outcome? 2. What's the simplest way to achieve that outcome? 3. What can we remove and still have something useful? 4. What assumptions can we validate with this MVP? 5. What would embarrass us if we shipped without it? (Only those are essential) ## Anti-Patterns to Avoid ### Over-Engineering - Adding configuration for things that could be hardcoded - Building abstraction layers "for future flexibility" - Implementing features "while we're in there" ### Premature Optimization - Performance tuning before measuring - Caching before proving it's needed - Scaling considerations for v1 ### Gold-Plating - Perfect error messages for unlikely scenarios - Comprehensive validation for internal tools - Beautiful UI for admin-only features ## Integration with Linear Workflow When this skill influences planning, the resulting Linear issues should: - Have clear, minimal acceptance criteria - Include a "Deferred" section documenting what's out of scope - Focus on vertical slices that could ship independently - Avoid sub-issues for "nice to have" features Remember: **"Ship the minimum that works."**
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.