| name | transversal-project-orchestrator |
| description | Orchestrates the generation of all artifacts for a 4Geeks Academy transversal project milestone — the universal project statement and the company-specific context files. Use this skill when a user wants to generate everything for a milestone at once, or when it is unclear whether they need only the README, only the CONTEXT files, or both. Trigger on phrases like "generate milestone N", "create all the files for hito X", "set up milestone N for these companies", or any request that involves a milestone number and one or more company descriptions without specifying which artifact they want. For targeted requests ("only generate the README", "only generate the context"), this skill will detect the intent and delegate accordingly. Always use this skill as the entry point when the scope of the request is ambiguous. |
4Geeks Academy — Transversal Project Generator (Orchestrator)
This skill is the single entry point for transversal project generation. It detects what needs to be produced and delegates to the appropriate specialized skill.
Step 1 — Detect What Is Needed
Before asking for any inputs, determine which artifacts the request requires:
| Situation | What to generate | Skills to invoke |
|---|
| No README exists for this milestone | README + all CONTEXT files | transversal-project-readme-generator → then transversal-project-context-generator |
| README exists, new company needed | CONTEXT file(s) only | transversal-project-context-generator |
| README exists, needs rewrite | README only | transversal-project-readme-generator |
| Explicit "everything" request | README + all CONTEXT files | Both skills in order |
If the situation is ambiguous, ask one clarifying question before proceeding:
Does a README already exist for this milestone, or does it need to be created?
Do not ask any other questions until this is resolved.
Step 2 — Collect Inputs for the Detected Scope
Collect only the inputs needed for the detected scope. Never ask for inputs that belong to an artifact that will not be generated.
If README needs to be generated, collect:
| Input | Description | Default |
|---|
milestone_number | Milestone number (e.g., 6) | — Must ask — |
milestone_topic | Core skill(s) this milestone teaches | — Must ask — |
milestone_position | early, mid, or late in the course | — Must ask — |
prior_milestones | What students have already built | — Must ask — |
tech_stack | Technologies required | — Must ask — |
template_repo | Starter repo URL | https://github.com/4GeeksAcademy/ai-engineering-company-project-monorepo |
authors | GitHub username(s) | — Must ask — |
If CONTEXT files need to be generated, collect:
| Input | Description | Default |
|---|
existing_readme | The milestone README — read it in full | — Must ask if not already available — |
company_scenarios | Company descriptions to generate CONTEXT files for | — Must ask — |
reference_context | An existing CONTEXT file for parity calibration | Optional |
If both README and CONTEXT are needed, collect all inputs together in a single round before generating anything.
Step 3 — Execute in Order
When both artifacts are needed, always generate the README first and the CONTEXT files second. The CONTEXT generator requires a completed README as input — it reads the README to extract the implied CONTEXT structure before writing anything.
Generating the README
Read and follow .cursor/skills/transversal-project-readme-generator/SKILL.md in full before writing any README content.
Generating the CONTEXT files
Once the README is complete (either just generated or provided as input), read and follow .cursor/skills/transversal-project-context-generator/SKILL.md in full before writing any CONTEXT content.
Pass the completed README as the existing_readme input to the context generator — even when it was just generated in the same session. The context generator must read it to extract the implied structure.
Step 4 — Delivery
Deliver files in this order:
README.md (if generated)README.es.md (if generated)CONTEXT-[slug].md for each company variant (if generated)
If only one type of artifact was generated, deliver only those files. Do not deliver placeholder or empty files for artifacts that were not requested.
Quality Self-Check
