Plan self validation
Skill lubochka/xiigen-mvp-engine/.claude/skills/universal/plan-self-validation
Self-building AI code generation engine that generates application flows instead of implementing them. AGPL-3.0.From the repository description
npx -y skills add lubochka/xiigen-mvp-engine --skill plan-self-validationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 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.9 KB, 311 tokens by cl100k_base, as published. Nobody here has run it
Plan Self Validation
Purpose
Use this as a private quality gate for plans so contradictions, missing steps, and unverifiable claims are removed early.
When to Use
Invoke after plan drafting and before asking for approval, executing, or assigning work.
Actions
- Map each requested deliverable to at least one plan step and one completion check.
- Ask what would make the plan fail: missing context, forbidden paths, concurrent edits, unavailable tooling, or ambiguous ownership.
- Check that each claim can be verified with a file read, command, test, or explicit user confirmation.
- Remove decorative process language that does not change execution.
- Revise the plan until it is shorter, stricter, and easier to audit.
XIIGen Adaptation
- When planning XIIGen implementation, validate that conventions are placed where they matter rather than pasted everywhere.
- Include DataProcessResult<T>, buildSearchFilter/buildSearchFilterFlat, Record<string, unknown>/unknown payloads, structured logging or local logger patterns, NestJS providers/injection tokens, and existing config helpers/defaults only for affected surfaces.
Avoid
- Do not treat plan self-validation as final verification of code or docs.
- Do not keep steps that cannot be observed or tested.
- Do not import source architecture, algorithms, design patterns, training, DPO, source domains, source classes, or source-specific paths.
Completion Signal
- The plan has no orphan requirements, no unverifiable completion claims, and no unnecessary source-derived assumptions.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.