Menú
Compares specification documents against implementation code to find divergences. Use when implementation of a spec or design doc is claimed complete.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Dispatches research agents to find real projects, papers, and documented failures before proposing any feature, architecture, or technology choice. Triggers on creative/design tasks, not on implementation of already-designed specs.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests.
Detects and prevents shortcut rationalization — when the agent is about to skip a step, simplify a requirement, or optimize away a constraint. Triggers proactively when rationalization patterns are noticed.
Provides a persistent cross-session task queue for work that should be done but isn't blocking current tasks. Enables background and future-session work tracking.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
Basado en la clasificación ocupacional SOC
| name | vibe-spec-vs-code-audit |
| description | Compares specification documents against implementation code to find divergences. Use when implementation of a spec or design doc is claimed complete. |
| user-invocable | true |
Specs drift from code. Code drifts from specs. This skill catches the gaps.
Identify the spec — Find the specification document (design doc, PRD section, API spec, etc.)
Identify the implementation — Find the code files that implement this spec
Line-by-line comparison — For each requirement/section in the spec:
Classify each gap:
Report:
Spec: [document name/path] Implementation: [code path(s)] Gaps Found: X (Y critical, Z high)
| GAP ID | Type | Severity | Spec Says | Code Does |
|---|---|---|---|---|
| GAP-AUTH-001 | Missing | Critical | "Tokens expire after 24h" | No expiration logic found |
