Menu
Audit SDD artifacts, requirement-task traceability, surface selection, and completion evidence before implementation or final delivery.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when locating, summarizing, auditing, or debugging Codex session rollout JSONL logs by CODEX_THREAD_ID, cwd, query, issue key, project path, child or inherited-history symptoms, malformed or huge log symptoms, permission concerns, or "what happened in this Codex thread" questions.
Use when auditing agent skills or plugins for safety, coverage, duplicated logic, token/context cost, prompt-contract risk, validation readiness, marketplace visibility, dependencies, network behavior, or install/update risk. For structural split/merge/move/delete/router decisions across skills or plugins, use capability-portfolio-architect instead.
Use when auditing agent skill/plugin portfolio architecture for cross-plugin capability overlap, weak routing, duplicated or missing skills, split/merge/delete/move decisions, shared capability extraction, reference/script extraction, or plugin boundary redesign. For safety, coverage, or validation review of a single artifact without boundary changes, use capability-auditor instead.
Use when performing broad external-first discovery, vetting, scoring, distillation, or synthesis of agent skills or plugin packs from the public web, GitHub/public repositories, OpenClaw/ClawHub, marketplaces, research sources, community implementations, user references, or local skills. Use for well-vetted capability synthesis, cross-skill comparison, plugin-pack synthesis, global capability acquisition, skill strengthening, and adoption/rejection changelogs.
Route and orchestrate agent skill and plugin lifecycle work. Use when work involves agent skills, plugins, marketplace packages, capability acquisition, synthesis, creation, installation, packaging, audit, or context-density optimization.
Use when creating, updating, validating, optionally installing/cache-refreshing, or handing off marketplace-backed agent plugins. Use for plugin manifests, local marketplace entries, plugin-pack synthesis, triggerable skill bundles, install visibility gates, and Codex app deeplinks.
| name | sdd-audit |
| description | Audit SDD artifacts, requirement-task traceability, surface selection, and completion evidence before implementation or final delivery. |
Use for SDD reviews, consistency checks, pre-implementation gates, completion proof, or questions like "is this spec ready", "are tasks traceable", or "can we claim done".
PowerShell: use $env:PLUGIN_ROOT for $PLUGIN_ROOT command paths.
python3 "$PLUGIN_ROOT/scripts/sdd_surface_audit.py" <repo> --json
python3 "$PLUGIN_ROOT/scripts/sdd_traceability_check.py" <repo> --json
Use --feature-dir <path> when active feature is not inferable.
FAIL: missing core artifact, unresolved high-impact clarification, buildable requirement without task, completed task without evidence, or LLM self-judgment used as proof.WARN: weak traceability, vague requirement, missing optional design detail, missing non-critical evidence ledger, or manual-only proof.PASS: artifacts are present and traceable enough for the chosen lane.## SDD Audit
- STATUS: PASS | WARN | FAIL
- LANE: <detected or selected lane>
- FEATURE_DIR: <path or none>
- BLOCKING_FINDINGS: <count and top findings>
- WARNINGS: <count and top findings>
- NEXT: <specific action>
Do not rewrite artifacts during an audit unless the user explicitly asks for fixes.