Create validation plan
Skill krzemienski/shannon-framework/skills/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.From its SKILL.md
npx -y skills add krzemienski/shannon-framework --skill create-validation-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
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.