Phase planning

Self-building AI code generation engine that generates application flows instead of implementing them. AGPL-3.0.From the repository description

Install

npx -y skills add lubochka/xiigen-mvp-engine --skill phase-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

19 days oldThe repository was created 19 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.

1.8 KB, 309 tokens by cl100k_base, as published. Nobody here has run it

Use this to convert a broad XIIGen task into small phases that can be implemented or reviewed independently without hidden dependencies.

Invoke when work spans multiple files, teams, skills, or verification gates, or when the user asks for phased delivery.

Define each phase by outcome, not by vague activity.
List inputs, allowed files, expected edits, and acceptance checks for each phase.
Place prerequisite discovery before design or implementation.
Attach a verification gate to every phase, scaled to risk and change size.
Mark handoff evidence: changed paths, commands run, decisions made, and remaining risk.

When a phase touches NestJS services, fabrics, providers, or factories, include checks for DataProcessResult<T> outcomes, Promise-based async shape, structured logging or local logger patterns, and provider/injection-token wiring.
When a phase touches data/search behavior, include buildSearchFilter/buildSearchFilterFlat use, Record<string, unknown>/unknown payload boundaries, and skipped empty criteria as acceptance checks.

Do not mix unrelated refactors into a phase.
Do not use phase names that hide deliverables without concrete acceptance checks.
Do not import source architecture, algorithms, design patterns, training, DPO, source domains, source classes, or source-specific paths.

Every phase has a bounded outcome, entry assumptions, exit evidence, and no hidden dependency on excluded source internals.

Read from the repository

Just SKILL.md. No reference files, no scripts.