← ClaudeAtlas

finishing-a-research-projectlisted

Use when a research project reaches completion — manuscript finalized, peer-review cleared, ready for publication / submission / archive. Runs the final checklist across rendering, BibTeX, wiki, data, reproducibility, archive, and follow-up grant planning.
leiverkus/research-superpowers · ★ 0 · Code & Development · score 72
Install: claude install-skill leiverkus/research-superpowers
# Finishing a Research Project The project is done only when the last checklist is green. This skill walks the final mile: rendering, archiving, DOI, submission, and optional grant follow-up. **Announce at start:** "Using finishing-a-research-project to close out `<slug>`." <SOFT-GATE> Before declaring "done", check every item on the Closing Checklist below. For unmet items: tell the user which, ask for a short reason per skipped item, write reasons into `knowledge/_meta/gate-overrides.log`, and mark the project in the log as either `status: done` (with documented omissions) or `status: paused`. Hidden partial completion is not closure — explicit justification is. </SOFT-GATE> ## Closing Checklist 1. **Manuscript renders cleanly** — `make render` in `output/publication/<book|article>/` exits 0; PDF/HTML opens without warnings 2. **Wiki lint green** — `python scripts/lint-wiki.py` exits 0 3. **BibTeX consistent** — every citation key in the manuscript exists in `references.bib`; no unused keys (or unused are intentional) 4. **Peer review done** — both constructive and adversarial reviewer reports archived under `output/publication/<target>/reviews/`; all Major issues resolved or explicitly deferred with rationale 5. **Hypothesis addressed** — pre-registered Hypothesis is explicitly confirmed, refuted, or marked "inconclusive — exploratory" in the manuscript 6. **Data reproducibility** — `output/data-analysis/` has `requirements.txt` or `environment.yml`; a README says "r