validate-plan
Validate that plan was correctly implemented, verify all success criteria
What this skill does
# Validate Plan
Validate that an implementation plan was correctly executed by comparing the plan's claims against the actual codebase state.
## Input
- If a plan path is provided, use it
- Otherwise, search `thoughts/shared/plans/` or ask the user
## Validation Steps
1. **Read the plan completely** — identify every phase, checkbox, success criterion, and manual verification item.
2. **Read every file the plan references** — source code, test files, config files. Compare what the plan says should exist against what actually exists.
3. **Run automated verification** — execute `make test` (or whatever the plan specifies). Capture full output.
4. **Compare plan claims to reality for each phase**:
- Do checked items (`[x]`) match what's actually in the code?
- Do function names, signatures, and behavior match what the plan specifies?
- Are there deviations (renamed functions, changed parameters, extra code not in plan)?
- Are there items marked complete that are missing or incomplete?
5. **Assess test quality** — don't just check that tests pass. Read the test code:
- Do tests actually assert the expected behavior, or are assertions missing/trivial?
- Do tests mock the method they're supposed to test (tautological tests)?
- Do the plan's success criteria have corresponding test assertions?
6. **Look for regressions** — did the implementation break pre-existing methods or behavior? Check methods that aren't part of the plan but exist in modified files.
7. **Evaluate plan quality** — if the plan has vague or unmeasurable criteria ("handle edge cases well", "good performance"), flag them as unverifiable rather than inventing interpretations.
## Report Format
```markdown
## Validation Report: [Plan Name]
### Implementation Status
Phase N: [Name] — [Fully implemented | Deviations found | NOT implemented]
### Automated Verification
[Full test output, pass/fail count]
### Findings
[What matches the plan, what deviates, what's missing, what's broken]
### Recommendations
[What needs fixing before this can be considered complete]
```
## Key Principles
- A passing test suite does not mean the plan is satisfied — tests can lie.
- Checked checkboxes do not mean work is done — verify against actual code.
- "It works" is not the same as "it matches the plan" — semantic mismatches matter.
- Vague criteria cannot be validated — flag them, don't rubber-stamp them.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.