exploring

Included with Lifetime

$97 forever

Use when a feature request needs user-facing decisions captured in history/<feature>/CONTEXT.md before Khuym planning. Clarifies fuzzy scope without implementation research or bead creation.

General

What this skill does


# Exploring Skill

If `.khuym/onboarding.json` is missing or stale, stop and invoke `khuym:using-khuym`.

Exploring turns fuzzy intent into locked decisions in `history/<feature>/CONTEXT.md`.

## Hard Gates

- Ask one question at a time; wait for the user before asking the next.
- Do not answer your own question.
- Do not research implementation, propose architecture, create beads, or write code.
- Do not invoke planning. End by handing the user to `khuym:planning`.

## Flow

1. **Scope**
   - Classify: `Quick`, `Standard`, or `Deep`.
   - Read `history/learnings/critical-patterns.md` and `.khuym/state.json` if present.
   - If the request spans independent subsystems, pick one and defer the rest.

2. **Domain**
   - Classify each applicable type:
     - `SEE`: user-visible surface
     - `CALL`: API, CLI, webhook, SDK, service interface
     - `RUN`: job, script, service, or pipeline
     - `READ`: docs, emails, reports, notifications
     - `ORGANIZE`: data model, file layout, taxonomy, config
   - Load `references/gray-area-probes.md` and choose only relevant probes.

3. **Gray Areas**
   - Generate 2-4 unstated product decisions that would make planning guess.
   - Do a quick scout only:
     ```bash
     rg "<feature-keyword>" src app packages --glob "*.{ts,tsx,js,jsx,py,md}" | head -20
     ```
   - Read 2-3 relevant files; cite existing patterns in questions.
   - Exclude implementation choices, performance tuning, and new scope.

4. **Socratic Locking**
   - Ask one concise question per message, preferably single-choice.
   - Start broad, then narrow into constraints.
   - After each decision, confirm it and assign a stable ID: `D1`, `D2`, `D3`.
   - For scope creep: mark it as deferred and return to the current question.

5. **Context Assembly**
   - Write `history/<feature-slug>/CONTEXT.md` from `references/context-template.md`.
   - Include boundary, domain types, locked decisions, scout paths, refs, questions, and deferred ideas.
   - Use concrete language. No placeholders, TODOs, or vague preferences.
   - Spawn one fresh reviewer with no history. Check completeness, contradictions, vague decisions, missing IDs, and blockers. Max two loops.

6. **State And Handoff**
   - Update `.khuym/state.json`:
     ```json
     {
       "active_skill": "exploring",
       "feature_slug": "<feature>",
       "phase": "exploring-complete",
       "summary": "Exploring complete. CONTEXT.md is ready for planning.",
       "next_action": "Invoke khuym:planning.",
       "focus": "history/<feature>/CONTEXT.md"
     }
     ```
   - Tell the user:
     ```text
     Decisions captured. CONTEXT.md written to `history/<feature>/CONTEXT.md`.
     CONTEXT.md is the source of truth for downstream agents.
     Invoke khuym:planning to research, propose phases/stories, and wait for approval.
     ```

Anti-patterns: bundled questions, deep implementation analysis, architecture proposals, beads, code, or skipping decision locking.

References: `references/gray-area-probes.md`, `references/context-template.md`.

Files: 3

Size: 7.3 KB

Complexity: 26/100

Category: General

Source: https://github.com/hoangnb24/skills/tree/main/plugins/khuym/skills/exploring

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts