菜单
Validate a MECE decomposition for compliance, structural integrity, and SDK readiness. Use when user says "validate decomposition", "check MECE compliance", "run validation", or wants to verify a decomposition tree passes quality gates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | validate |
| description | Validate a MECE decomposition for compliance, structural integrity, and SDK readiness. Use when user says "validate decomposition", "check MECE compliance", "run validation", or wants to verify a decomposition tree passes quality gates. |
| metadata | {"author":"Fred Bliss","version":"0.4.1","last_verified":"2026-04-02"} |
Check a MECE decomposition for structural integrity, MECE compliance, and Agent SDK readiness.
/validate <decomposition JSON or file path>
Examples:
/validate then paste decomposition JSON/validate output.json/validate after a /decompose or /interview session (validates the last output)uv run mece-decomposer/skills/mece-decomposer/scripts/validate_mece.py <decomposition.json>
Checks:
atom_spec, all branches have orchestration)Using the scoring rubrics from the mece-decomposer skill:
## Validation Report
**Status:** PASS / FAIL
**ME Score:** 0.XX -- [interpretation]
**CE Score:** 0.XX -- [interpretation]
**Overall:** 0.XX -- [interpretation]
### Issues
| Severity | Location | Type | Description |
|----------|----------|------|-------------|
| error | node:1.2 | gap | Missing ... |
| warning | node:2 | depth| Tree depth ... |
### Recommendations
- [Fix for each error]
- [Improvement for each warning]
The mece-validate MCP tool renders a visual report with clickable issue locations that navigate to the problem node in the tree.
| Range | ME | CE |
|---|---|---|
| 0.85-1.0 | Strong: no overlap | Strong: no gaps |
| 0.70-0.84 | Acceptable: minor boundary issues | Acceptable: minor gaps documented |
| 0.50-0.69 | Weak: redefine boundaries | Weak: add missing components |
| < 0.50 | Failed: re-cut this level | Failed: restructure |
Quality gate: >= 0.70 for export, >= 0.85 for confidence.
/validate/exportOpt the current project into down-tier model delegation by installing a standalone .claude/rules/model-delegation.md rule, optionally with pre-shaped .claude/agents/ definitions (fast-executor, task-coder) and an optional agent-state feedback layer. The rule tells Claude to route well-specified data and coding tasks to a cheaper model in a subagent, keeping judgment-heavy work in the main loop. Use when the user says "set up model routing", "set up model delegation", "use cheaper models for subagents", "delegate to a lower-power model", or wants to remove or update that rule.
Pre-share scan for leaked secrets and privacy-sensitive content. Wraps simonw/scan-for-secrets for literal matching (with JSON/URL/HTML/backslash/unicode escape variants) and composes a ripgrep regex pass for shape-based leaks (other users' home paths, emails, IPv4, MAC, JWTs, API keys). Use when user says "scan for secrets", "check for leaked credentials", "pre-share scan", "redact home paths", "PII scan", "strip my username from transcripts", "scan logs before publishing", "check before sharing", "audit before commit", "find leaked API keys", "scan agent transcript".
Convert JavaScript and TypeScript projects to use bun instead of npm/yarn/pnpm. Use when user asks to "migrate from npm to bun", "convert to bun", "switch package managers", "replace npm", or "use bun instead". Includes conversion tables and lock file migration. Core conventions auto-loaded via SessionStart hook; invoke /dev-conventions:bun-tooling for full reference.
Audit project dependencies for known vulnerabilities using uv audit (Python) and bun audit (JS/TS). Use when user says "audit dependencies", "check for vulnerabilities", "security audit", "check deps", "are my packages safe", "CVE check", "dependency security", "vulnerability scan". Invoke with /dev-conventions:dep-audit.
Documentation conventions: last-updated dates, lowercase filenames, internal/ subfolder for non-shared docs, session logs, and documenting the "why". Use when creating or updating documentation, READMEs, or design docs. Invoke with /dev-conventions:doc-conventions. Triggers on "write docs", "update README", "document this", "add a design doc", "session log".
Detailed Python/uv conversion reference. Core conventions auto-loaded via SessionStart hook; invoke /dev-conventions:python-tooling for full conversion tables. Use when you need the complete uv command mapping, version pinning strategy, or lock file workflow.