idea-refine
Structured divergent/convergent thinking to turn vague ideas into concrete proposals. Use when you have a rough concept that needs exploration before committing to a spec.
What this skill does
# Idea Refine ## Overview Turn vague product ideas or technical concepts into concrete, evaluable proposals through structured divergent and convergent thinking. This skill runs before `spec-driven-development` when the problem space is still ambiguous. ## When to Use - A feature request is vague or open-ended - You have competing approaches and need to evaluate tradeoffs - A stakeholder describes a problem without a clear solution - You need to explore the design space before committing to a direction ## Process ### Step 1: Problem Framing State the problem clearly: - Who is affected - What outcome they need - What constraints exist - What success looks like ### Step 2: Divergent Exploration Generate multiple approaches without judgment: - List at least three substantially different solutions - Include at least one unconventional approach - Note assumptions each approach depends on - Identify risks unique to each approach ### Step 3: Convergent Evaluation Score each approach against: - User impact: how well it solves the stated problem - Implementation cost: time, complexity, and dependencies - Risk: what could go wrong and how recoverable it is - Extensibility: how well it supports future related work ### Step 4: Proposal Write a concise proposal covering: - Recommended approach and why - Key tradeoffs accepted - Assumptions that need validation - Open questions for the team ## Common Rationalizations | Rationalization | Reality | |---|---| | "The first idea is usually fine" | First ideas tend to be the most obvious, not the most effective. | | "We can refine later" | Later refinement is more expensive than early exploration. | | "This is too small for structured thinking" | Even small features benefit from a minute of structured evaluation. | ## Verification - [ ] Problem is stated clearly with affected users - [ ] At least three approaches were considered - [ ] Each approach was scored against consistent criteria - [ ] A clear recommendation exists with accepted tradeoffs documented ## Anti-Rationalization Table | Excuse | Counter | |--------|---------| | "The first idea is usually fine" | First ideas tend to be the most obvious, not the most effective. | | "We can refine later" | Later refinement is more expensive than early exploration. | | "This is too small for structured thinking" | Even small features benefit from a minute of structured evaluation. | | "Three approaches is too many for this" | Two approaches is the minimum for comparison. Three reveals non-obvious options. | | "The stakeholder already knows what they want" | Stakeholders describe problems, not solutions. Explore the solution space. |
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.