validating

Included with Lifetime

$97 forever

Use when planning has an approved work shape and needs feasibility validation before swarming.

General

What this skill does

# Validating

If `.khuym/onboarding.json` is missing or stale for the current repo, stop and invoke `khuym:using-khuym` before continuing.

Validating is the hard gate between planning and execution. It rejects beautiful fantasy plans by requiring repo/system evidence, feasibility proof, and current-story readiness.

## Required Inputs

- `history/<feature>/CONTEXT.md`
- `history/<feature>/discovery.md`
- `history/<feature>/approach.md`
- approved shape artifact: direct note, spike question, small plan, `phase-plan.md`, or `epic-map.md`
- mode-required current-work artifacts: `current-story-pack.md`, `phase-<n>-contract.md`, or story map
- `.beads/` for the current execution surface when beads are required

If any mode-required input is missing, return to `khuym:planning`. If the shape artifact has not been approved by the user, stop immediately.

## Operating Contract

1. Orient on state, mode, approved shape, and current artifacts.
2. Run the reality gate: mode fit, current repo truth, assumptions, and smaller-path challenge.
3. Build the feasibility matrix from concrete evidence: code, inspection, commands, tests, docs/version proof, runtime probe, or `.spikes/`.
4. Require spike/probe work for unproven assumptions that can invalidate the current story/shape.
5. Check integration readiness and current-story readiness before bead review.
6. If beads are required but absent after READY, return to planning to create current-story/work beads, then resume validation.
7. Polish/review only validated current-story/work beads.
8. Ask the user to approve execution for this work only.

Load `references/validation-reference.md` for the detailed checklist, repair routing, spike handling, approval gate, and subagent prompts.

## Non-Negotiable Gates

- No source-editing execution before explicit user approval.
- Maximum 3 structural-verification iterations. Do not attempt iteration 4.
- A failed reality gate or `NO` spike result returns the workflow to `khuym:planning`.
- A plan with only plausibility language and no concrete evidence is NOT READY.
- All CRITICAL fresh-eyes findings must be fixed before approval.
- Approval is for the current work only. Future work returns to planning/validating.

## Approval Outcome

When the user approves, update `.khuym/state.json` so the next action is swarming:

```json
{
"active_skill": "validating",
"feature_slug": "<feature-name>",
"phase": "validated",
"mode": "<mode>",
"current_work": "<story/direct/phase>",
"summary": "Current work passed feasibility validation and is ready for swarming.",
"next_action": "Invoke khuym:swarming for the validated work."
}
```

Then hand off: `Validation complete. Current work passes. Invoke khuym:swarming skill.`

## Reference Files

| File | When to Load |
|---|---|
| `references/validation-reference.md` | Validation phases, repairs, approval, plan-checker, bead-reviewer |

Files: 2

Size: 8.0 KB

Complexity: 25/100

Category: General

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

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