Add project-ci-generator skill

[vitaliiivanovspryker]

What

Adds a new skill project-ci-generator under plugins/spryker-ai-dev-sdk/skills/.

It transforms a heavy product/vendor-style CI setup into a single, lean project CI pipeline.

How it works

1. Discover — reads whatever CI actually exists (for a Spryker project the base is .github/workflows/ci.yml), including any inline [project applicable] / [remove for project] recommendation markers. Nothing is assumed — CI contents change over time.
2. Ask — short questionnaire: target platform (GitHub/GitLab/Bitbucket/other), which suites to keep, single version vs. matrix, notifications, wipe scope.
3. Propose — derives a keep/drop plan from discovery + answers and gets user approval before touching anything (CI changes are outward-facing and hard to reverse).
4. Rebuild — writes one project CI from the surviving jobs (commands reused verbatim), keeps only the support files those jobs reference, drops the rest.
5. Validate + quality gate — a checklist that guarantees a single pipeline, all unneeded files removed, no orphan/dangling references, only approved jobs, and no product-only jobs survive (compatibility matrices, full QA/e2e suites, release/upmerge automation, product doc publishing).

Design principles

• Investigate, never assume — no remembered job list or filename is trusted.
• Transform, don't template — reuses the existing CI's real, environment-correct commands.
• Propose before acting — approval gate before any deletion.

Files

• SKILL.md — the skill (frontmatter name + description, matches repo convention).
• README.md — overview + a Mermaid flow diagram (mirrors static-validation, which also ships a README).

Testing

Validated end-to-end on a real Spryker project CI (sandbox copy): 18 CI files reduced to 3 (one project pipeline + the single referenced deploy descriptor + PR template), with the full quality-gate checklist passing 14/14.