hoangnb24/validating
plugins/khuym/skills/validating/SKILL.md
Use when planning has an approved work shape and needs feasibility validation before swarming.
$ install --global
skillsauthnpx skillsauth add hoangnb24/skills validatingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 2:45 AM39.0s2 files scanned
SKILL.md
- name:
- validating
- description:
- >-
- version:
- 1.2
- position:
- 3
- chain:
- exploring -> planning -> validating -> swarming
- ecosystem:
- khuym
- kind:
- command
- command:
- bv
- missing_effect:
- unavailable
- reason:
- Validation depends on bv graph checks for polishing and risk review.
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.mdhistory/<feature>/discovery.mdhistory/<feature>/approach.md- approved shape artifact: direct note, spike question, small plan,
phase-plan.md, orepic-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
- Orient on state, mode, approved shape, and current artifacts.
- Run the reality gate: mode fit, current repo truth, assumptions, and smaller-path challenge.
- Build the feasibility matrix from concrete evidence: code, inspection, commands, tests, docs/version proof, runtime probe, or
.spikes/. - Require spike/probe work for unproven assumptions that can invalidate the current story/shape.
- Check integration readiness and current-story readiness before bead review.
- If beads are required but absent after READY, return to planning to create current-story/work beads, then resume validation.
- Polish/review only validated current-story/work beads.
- 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
NOspike result returns the workflow tokhuym: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:
{
"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 |
Related Skills
hoangnb24/smart-commits
tools
VerifiedTrustedCommunity
Use when the user asks to commit everything, smart commit, group commits, organize staged or unstaged changes, create logical commits, push current work, or preserve a clean commit stack from an existing working tree.
215SKILL.mdUpdated May 21, 2026
hoangnb24/using-khuym
development
VerifiedTrustedCommunity
Use when starting or resuming any Khuym project session, choosing the next Khuym skill, running go mode, checking onboarding/scout state, or enforcing workflow gates. Bootstrap meta-skill for routing across the Khuym agentic development ecosystem.
215SKILL.mdUpdated Apr 18, 2026
hoangnb24/goal-griller
development
VerifiedTrustedCommunity
Use when the user wants to turn a rough idea, vague task, feature wish, bug-fix intent, or Codex /goal objective into a clear verifiable goal prompt. Use when the user mentions goal mode, /goal, set_goal, long-running autonomous Codex work, or asks to be interviewed/grilled before creating a goal.
213SKILL.mdUpdated May 19, 2026
hoangnb24/concept-game-builder
tools
VerifiedTrustedCommunity
Use when Codex should turn a concept, topic, tutorial, lesson, algorithm, system, workflow, or abstract idea into a playable browser game that teaches through interaction. Use for planning or implementing educational web games with the Game Studio plugin, including concept-to-mechanic translation, gameplay loop design, learning progression, and browser-game QA.
213SKILL.mdUpdated May 19, 2026