Individual skill

manage-project

Use when managing a manuscript project over time. Scaffolds the project structure, tracks writing progress across phases, maintains project memory files, and generates submission checklists and backwards timelines (commands init, status, sync-memory, checklist, timeline).

skills/manage-project/SKILL.md

Read pinned source

Source commit cc462bc2069064b557c2fea12a1f83ed1fe67f66

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 373
Repository last updated: Nov 2, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

biostatistics Repository topic
claude-code Repository topic
claude-skills Repository topic
clinical-research Repository topic
diagnostic-accuracy Repository topic
literature-review Repository topic
manuscript Repository topic
medical-ai Repository topic
medical-research Repository topic
meta-analysis Repository topic
writing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,375 bytes
SKILL.mdcore · 6,375 bytes
SKILL.mdcore · 6,375 bytes
SKILL.mdcore · 6,375 bytes
references/init_scaffold.mddoc · 2,445 bytes
references/pre_submission_checklist.mddoc · 2,329 bytes
references/project_state_template.jsonasset · 818 bytes
references/scaffold_templates.mddoc · 1,228 bytes
references/status_output_format.mddoc · 1,153 bytes
references/timeline_example.mddoc · 812 bytes
scripts/init_project.pyruns · 10,183 bytes
scripts/migrate_project_to_ssot.pyruns · 8,236 bytes
scripts/validate_project_contract.pyruns · 9,452 bytes
skill.ymlasset · 1,338 bytes
templates/SSOT.yaml.templateasset · 1,189 bytes
tests/test_ssot_mark_complete.shruns · 4,871 bytes

Read excerpt


# Manage-Project Skill -- Research Project Management

## Commands

### `/manage-project init {name} --type {type} --journal {journal} [--ssot] [--zotero-collection NAME]`

**Parameters:**
- `{name}` -- Project identifier (e.g., `nnunet-skull-fracture`, `rfa-meta-analysis`)
- `--type` -- Paper type: `original | meta | case | animal | technical | ai_validation | letter`
- `--journal` -- Target journal: `RYAI | AJR | Radiology | European_Radiology | KJR | INSI | AJNR | generic`
- `--ssot` -- Emit `SSOT.yaml` (schema v1) from `templates/SSOT.yaml.template` instead of legacy `project.yaml`. Required, but not sufficient, for Phase 1C auto-enforce (the PostToolUse verify-refs hook blocks instead of warns): enforce also needs `qc/migration_complete`, which init does not write. After init, run `migrate_project_to_ssot.py --project-root {target_dir} --mark-complete` to validate the SSOT.yaml and write the marker. New projects should pass `--ssot`; legacy in-flight projects stay on `project.yaml` until `/manage-project migrate-ssot` is run.
- `--zotero-collection NAME` -- Optional. Create a Zotero collection via pyzotero and populate `library_id` + `collection_key` in the contract. Requires `ZOTERO_API_KEY` + `ZOTERO_LIBRARY_ID` (optionally `ZOTERO_LIBRARY_TYPE`, default `user`). With pyzotero or the credentials missing, the contract is scaffolded with `library_id: null` / `collection_key: null` and a WARN is printed.

**SSOT template substitutions:** `{{PROJECT_ID}}` → `{name}`; `{{PROJECT_TYPE}}` → the SSOT