brainstorm-sync
Capture brainstorm discoveries that aren't in the plan — the thinking that makes this project unique
What this skill does
# Brainstorm Sync After brainstorming, capture the THINKING that didn't make it into the plan. The plan has workflows and features. This captures WHY and WHO and WHAT WE SAID NO TO. ## What to Capture From the brainstorm conversation, extract: ### 1. User Insight (from User Day-In-Life) The specific person, their context, their pain. This grounds all future decisions. → Write to `.feat-tree/memories/user.md` ```markdown # User **Who:** [Name, role, context] **When problem appears:** [Specific moment in their day] **Current workaround:** [What they do now] **Pain:** [What's frustrating about it] ``` ### 2. Scope Fence (from Scope Fence) What we explicitly said NO to. Prevents scope creep in future sessions. → Write to `.feat-tree/memories/scope.md` ```markdown # Scope **This IS:** [One sentence] **This is NOT:** - [Explicit exclusion] - [Explicit exclusion] **Features we said no to:** - [Feature]: [Why not] ``` ### 3. Core Assumption (from Crux) The ONE thing that must be true. Future sessions should validate this. → Update `.feat-tree/CONTEXT.md` Key Assumptions section ```markdown ## Key Assumptions - [untested] [The core assumption] — test by [how to validate] ``` ### 4. Risks (from Pre-Mortem) How this fails. Future sessions should watch for warning signs. → Write to `.feat-tree/memories/risks.md` ```markdown # Risks **"It failed because..."** 1. [Failure mode] — Watch for: [early warning sign] 2. [Failure mode] — Watch for: [early warning sign] **Mitigations:** - [What we're doing to prevent] ``` ### 5. Design Rationale (from Design phase) WHY we chose this approach over alternatives. Prevents revisiting decisions. → Write to `.feat-tree/memories/decisions.md` ```markdown # Design Decisions **[Topic]:** [Choice] - Considered: [Alternative 1], [Alternative 2] - Chose because: [Why this fits better] - Trade-off accepted: [What we gave up] ``` ## Process 1. **Review brainstorm conversation** — What thinking happened that's NOT in the plan? 2. **Extract each category above** — Only if it was actually discussed 3. **Write to memory files** — Dense, not verbose 4. **Update CONTEXT.md** — If core assumptions or project understanding changed ## What NOT to Capture - Stuff already in the plan (workflows, features, implementation order) - Generic/speculative content (only capture what was actually discussed) - Session-specific details that won't help future sessions ## Confirm ``` Synced brainstorm discoveries: - memories/user.md — [created/updated] - memories/scope.md — [created/updated] - memories/risks.md — [created/updated] - memories/decisions.md — [created/updated] - CONTEXT.md — [updated assumptions] Future sessions will have this context. ```
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.