Workspace Templates

// Traduce tutti i file di una cartella Drive in un'altra cartella e mantiene le sottocartelle: sorgente/a/b/c/d.pdf diventa destinazione/a/b/c/d.<lingua>.pdf e d.<lingua>.bilingual.pdf, con ogni pagina originale accanto alla sua traduzione. Ogni file conserva l'impaginazione e passa i controlli del Traduttore PDF (nessun testo lasciato non tradotto, nessun numero cambiato); Word, PowerPoint e testo vengono tradotti dal PDF che Drive ne ha fatto. Prima di tradurre l'agente mostra l'elenco dei file e chiede conferma, poi crea sul canvas una sezione per ogni file e li traduce tutti con un solo avvio, in parallelo: un file non riuscito ferma solo la sua sezione. Alla fine riporta l'esito di ogni file. Translates every file of a Drive folder into another folder and keeps the sub-folders: source/a/b/c/d.pdf becomes destination/a/b/c/d.<lang>.pdf and d.<lang>.bilingual.pdf, with each original page beside its translation. Each file keeps its layout and passes the PDF Translator's checks (no text left untranslated, no number changed); Word, PowerPoint and text files are translated from the PDF Drive made of them. Before translating, the agent shows the file list and asks to confirm, then builds one section per file on the canvas and translates them all in one run, in parallel: a file that fails stops only its own section. At the end it reports every file's outcome.

// Build software in your GitHub repository: a landing page, a website, a web app, an API or a new feature in an existing product. Plan it the way gstack does, then build it in parallel coding lanes. An office-hours interview in the chat produces a design doc; gstack's reviews (spec, CEO, design, developer experience, engineering) settle every decision with you; the approved tasks become up to 4 coding lanes, each on its own branch of your GitHub repository, each opening a draft pull request. The pull requests you pick are merged into one working branch, which opens as a single pull request for you to merge on GitHub. Nothing touches GitHub until you approve — you can also create the lanes without starting them. Needs a GitHub connection with write access to the repository. Costruisci software nel tuo repository GitHub: una landing page, un sito web, una web app, un'API o una nuova funzionalità di un prodotto esistente. Pianificalo come fa gstack, poi costruiscilo in lane di codice parallele. Un'intervista in chat produce un design doc; le review di gstack (spec, CEO, design, developer experience, engineering) fissano ogni decisione con te; i task approvati diventano fino a 4 lane, ognuna su un proprio branch del tuo repository GitHub, ognuna con una pull request in bozza. Le pull request che scegli vengono unite in un unico branch di lavoro, che si apre come una sola pull request da unire tu su GitHub. Nulla tocca GitHub prima della tua approvazione. Richiede una connessione GitHub con accesso in scrittura.

// Syncs an Odoo Sales + Invoicing instance into the organization ontology: courses, learners, cohorts, enrollments and invoices, with the typed links between them. Idempotent — re-running upserts rather than duplicating. Use when a source system has no native Drive adapter and the workspace itself has to be the pipeline.

// Builds a board-ready business review deck for a course business from the organization ontology and live Odoo invoices: revenue by month and by course, enrollment and completion figures, and the actions they imply. Outputs an HTML deck and a downloadable PowerPoint. A second application on the same ontology — it defines no model and ingests nothing.

// An operations console for a course business, built on the organization ontology. Reads learners, cohorts, enrollments and courses from the graph, joins them to live Odoo invoices, and sorts every learner into one bucket: overdue, paid-but-inactive, at risk, ready to upsell, or healthy. Drafts re-engagement outreach, and on request writes the follow-up back to Odoo and stamps it on the ontology.

// Maps course documents already in Drive onto the organization ontology as CourseMaterial objects, linked to the Course they belong to. The assignment rule lives on the canvas as an editable JSON node, because nothing in Drive states which course a document serves — that mapping is a modelling choice.