Thesis Engine
estevanhernandez-stack-ed/Thesis-Engine
Descobre tópicos de tese vivos e reúne fontes em cinco eixos
Ver no GitHubSkill que automatiza o cold-start de teses acadêmicas, descobrindo tópicos relevantes com baixa concorrência e coletando fontes de pesquisa estruturadas em cinco eixos (antecedentes, metodologia, posições opostas, autores-chave, fontes primárias). Gera uma pasta de execução pronta para integração com vibe-thesis e ThesisStudio, emitindo proposta, notas estruturadas e referências BibTeX validadas.
Instalação
npx convez-ai estevanhernandez-stack-ed/Thesis-Engine1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Acelerar a fase de pesquisa inicial de trabalhos acadêmicos
- Estruturar coleta de fontes em múltiplos eixos de investigação
- Gerar esboços de tese prontos para edição e refinamento
Veredito

Ferramenta focada e não-destrutiva que resolve um problema real no fluxo de escrita acadêmica: o trabalho chato do cold-start. Bom design com gates de qualidade e integração clara com ecossistema vibe-thesis, mas escopo limitado a um estágio específico da tese.
README
A tradução para o português deste README ainda está na fila.
Thesis Engine
A research feeder for vibe-thesis projects — it does the cold-start work, so the drafting can start warm.
What it does
Thesis Engine handles the painful part of starting a thesis — finding a live topic and pulling the first wave of sources — and hands you a vibe-thesis-shaped run folder ready to drop into ThesisStudio.
- Discover — scans a field for live, low-competition thesis topics and ranks five candidates.
- Gather — pulls sources across five research axes: prior art, methodology survey, opposing positions, key authors, and primary sources.
- Cite — emits a BibTeX
references.bibwith a Pandoc citation key on every source, each tagged verify before citing until you've checked it. - Adapt (optional) — distills a gathered run into a Smart Brevity blog draft for BlogStudio.
It produces the inputs. The drafting itself stays inside vibe-thesis — that's where the LeadWriter persona, the citation render pipeline, and the three-pillar voice live.
How it works
Three stages run as one command or piece by piece:
/thesis-engine:run # Stages 1 → 2 (add --blog for Stage 3)
/thesis-engine:run --domain X --auto # auto-pick top topic, no confirmation
/thesis-engine:discover --domain X # Stage 1 only — a ranked topic table
/thesis-engine:write "your own topic" # Stage 2 only — gather sources for a topic you bring
/thesis-engine:blog ./run-folder/ # Stage 3 only — adapt a run into a blog draft
- Output mirrors the vibe-thesis Template exactly. A dated
thesis-engine-run-YYYYMMDD/folder holds01_PLANNING/proposal.md,02_RESEARCH/<axis>/notes.mdfor each of the five axes, and05_CITATIONS/references.bib. The subdirectory names match, so ingesting is a copy — drop01_PLANNING/,02_RESEARCH/, and05_CITATIONS/into ThesisStudio, append the.bibentries to your canonical bibliography, then keep going inside vibe-thesis. - Quality gates run before a run completes. At least twelve sources across the five axes, a Pandoc key on every source,
[@key]references in every notes file, a cleanly-parsingreferences.bib, an explicit thesis claim inproposal.md, and a Summary section per axis. Fail a gate and the partial run moves topending/with the failed gates surfaced as a checklist. - Non-destructive by design. It writes to a dated run folder; you (or a future ingest skill) copy subdirs across. It's a feeder, not a citation manager and not a thesis writer.
Run folder structure
Every run produces a dated folder mirroring the vibe-thesis Template:
thesis-engine-run-YYYYMMDD/
├── README.md (run summary + ingest instructions)
├── topics.md (Stage 1 ranking)
├── 01_PLANNING/
│ └── proposal.md
├── 02_RESEARCH/
│ ├── prior-art/notes.md
│ ├── methodology-survey/notes.md
│ ├── opposing-positions/notes.md
│ ├── key-authors/notes.md
│ └── primary-sources/notes.md
├── 05_CITATIONS/
│ └── references.bib
└── blog/ (only if --blog or /thesis-engine:blog)
└── 02_DRAFTS/
└── YYYY-MM-DD-[slug]/
├── POST.md
└── frontmatter.yaml
Validated on
Fed research across the full 626 Labs article catalog.
Install
Stable (recommended) — as a Claude Code plugin via the marketplace:
/plugin marketplace add estevanhernandez-stack-ed/vibe-plugins
/plugin install thesis-engine@vibe-plugins
Canary — track this repo's main:
/plugin install thesis-engine@estevanhernandez-stack-ed/Thesis-Engine
For Cowork, drag the bundled thesis-engine.plugin archive from a release into the app.
Pairs with vibe-thesis and ThesisStudio
Thesis Engine is the front of a longer pipeline. It seeds the research; vibe-thesis drafts the paper; ThesisStudio and BlogStudio are the workspaces the output lands in.
- ThesisStudio receives
01_PLANNING/,02_RESEARCH/, and05_CITATIONS/. Strip the verify before citing note from.bibentries once you've confirmed them. - BlogStudio receives
blog/02_DRAFTS/<dated-slug>/when you ran with--blog. - vibe-thesis picks up from there — the LeadWriter persona, the research swarms, and the render pipeline.
Each successful run optionally logs a completion entry to the 626 Labs dashboard. If the MCP is unavailable, the run still completes — you just don't get the activity-log entry.
Part of the Vibe ecosystem
Part of the Vibe Plugins marketplace from 626 Labs — foundations and process pillars for AI-assisted creation.
/plugin marketplace add estevanhernandez-stack-ed/vibe-plugins
Credit
Built by Estevan Hernandez — 626 Labs.
License
MIT — Imagine Something Else.