create-validation-plan

Included with Lifetime

$97 forever

---

General

What this skill does

---
name: create-validation-plan
description: Multi-phase project plan generator that injects functional validation gates with evidence requirements. Output: phase plans with gates per real-system PASS criterion.
triggers:
  - "create validation plan"
  - "validation phases"
  - "inject validation gates"
  - "plan with gates"
---

# create-validation-plan

Backs the gate-injection step of `/shannon:plan-deep` and the planning phase of `/shannon:validate`.

## Behavior contract

1. Read a base plan (from `plan-author`) OR a feature brief.
2. For each phase in the plan: derive a validation gate.
3. Gate structure (per phase):
   ```markdown
   ## Validation Gate (phase NN)
   - **Skill:** functional-validation | visual-inspection | api-validation | ...
   - **Real system to exercise:** <server | simulator | CLI invocation>
   - **Journey to execute:** <step-by-step actions>
   - **Evidence required:** <screenshot | response body | log tail>
   - **PASS criterion:** <specific assertion>
   - **FAIL → consequence:** halt + refusal-discipline OR retry via /shannon:fix
   ```
4. Emit the gate inline in the phase file (NOT a separate file — gate is part of the phase).
5. Refuse if the base plan has a phase claiming "tests pass" or "test coverage" as a gate — these are the patterns Shannon's iron rule forbids.

## When to use

- Phase 3 of `/shannon:plan-deep`
- Phase 1 of `/shannon:validate` (planning)
- Standalone gate-injection on an existing plan that lacks them

## When NOT to use

- Read-only changes (audits, doc updates)
- Pure refactor with no behavior change

## Iron rules

- **No mock-based gates.** Gate must exercise real system.
- **No "tests pass" gates.** Refuse and rewrite.
- **Evidence path specified at gate definition time** — not deferred.
- Gate is part of the phase, not a separate optional step.

Files: 1

Size: 1.8 KB

Complexity: 3/100

Category: General

Source: https://github.com/krzemienski/shannon-framework/tree/main/skills/create-validation-plan

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts