Skill

create-validation-plan

Multi-phase project plan generator that injects functional validation gates with evidence requirements. Output: phase plans with gates per real-system PASS criterion.

npx claudepluginhub krzemienski/shannon-framework --plugin shannon

Popularity

Stars

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/shannon:create-validation-plan

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

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

SKILL.md

49 lines · ~460 tokens

Similar Skills

ui-ux-pro-max

90.2k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

55.5k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

gitnexus-exploring

38.9k

Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.

1 file

gitnexus

Stats

LanguagePython

Stars2

MaintenanceExcellent

Last CommitMay 24, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

create-validation-plan

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

Behavior contract

Read a base plan (from plan-author) OR a feature brief.

For each phase in the plan: derive a validation gate.

Gate structure (per phase):

## 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

Emit the gate inline in the phase file (NOT a separate file — gate is part of the phase).

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.