Top CS Paper Workflow
Coordinate work; do not replace the six specialist skills. Use this skill only when the user wants a project-level view or to resume a multi-stage paper workflow.
Start safely
Ask for the paper project root. Never search the home directory, cloud folders, or other projects.
Initialize the project-local state only after the user has chosen that root:
python scripts/paper_workflow.py init --project <project-root>
The tool writes only <project-root>/.top-cs-paper/workflow.yaml. It stores structured IDs, relative file paths, file metadata, and SHA-256 hashes; it never copies manuscript, PDF, data, reviewer text, or citation content.
Use inventory only with explicit relative --include paths. Do not infer that every file in a project is in scope.
Coordinate the six skills
Follow this order when the relevant stage applies. A stage may be marked not-applicable; do not invent missing work to make it pass.
| Stage |
Owner |
Required handoff |
| Contribution and argument |
top-cs-writing |
claim IDs, evidence needs, manuscript plan |
| Literature evidence |
top-cs-evidence |
citation ledger and claim-to-source map linked to claim IDs |
| Figures |
top-cs-figure |
figure briefs linked to claims and evidence |
| Manuscript refinement |
top-cs-polishing |
terminology and revision notes |
| Pre-submission risk audit |
top-cs-reviewer |
review issues, threatened claims, proposed actions |
| Response and verified change |
top-cs-response |
revision IDs linked back to review issues |
top-cs-figure is the only renderer. This workflow may request or validate a figure handoff, but never renders a figure itself.
Record only traceability
Use workflow-manifest.schema.yaml and references/handoff-and-checkpoints.md as the project contract. Maintain stable IDs and links:
claim -> evidence -> figure
claim -> review issue -> revision
Expected observations, planned figures, and unresolved reviewer issues are not completed results. Preserve those states explicitly.
Check status
python scripts/paper_workflow.py inventory --project <project-root> --include paper/main.tex
python scripts/paper_workflow.py status --project <project-root>
python scripts/paper_workflow.py status --project <project-root> --format json --strict
Normal status output is advisory and exits successfully when the manifest is structurally valid. --strict exits non-zero for incomplete checkpoints, missing links, unverified evidence, or pending author confirmation. It does not claim that a paper is accepted or technically correct.
Boundaries
- Do not fabricate experiments, figures, citations, reviewer comments, venue rules, or completion evidence.
- Keep all tracked paths project-relative and inside the chosen project root. Reject absolute paths, traversal, missing files, and escaping symlinks.
- Use current official venue sources through the specialist skills; a workflow status is not a policy source.
- Do not overwrite an existing manifest without the user's explicit
--force request.
Resources
scripts/paper_workflow.py: initialize, inventory explicitly selected files, and inspect project traceability.references/handoff-and-checkpoints.md: checkpoint meanings and cross-skill handoff rules.../_shared/contracts/workflow-manifest.schema.yaml: public schema for the project state file.
1---2name: top-cs-paper-workflow3description: Coordinate a complete evidence-grounded CS paper project across the six Top CS skills. Use when work spans contribution planning, literature evidence and figure handoff, manuscript revision, pre-submission review, or reviewer response and needs resumable project status. Do not use for a single specialist task.4---56# Top CS Paper Workflow78Coordinate work; do not replace the six specialist skills. Use this skill only when the user wants a project-level view or to resume a multi-stage paper workflow.910## Start safely11121. Ask for the paper project root. Never search the home directory, cloud folders, or other projects.132. Initialize the project-local state only after the user has chosen that root:1415 ```text16 python scripts/paper_workflow.py init --project <project-root>17 ```18193. The tool writes only `<project-root>/.top-cs-paper/workflow.yaml`. It stores structured IDs, relative file paths, file metadata, and SHA-256 hashes; it never copies manuscript, PDF, data, reviewer text, or citation content.204. Use `inventory` only with explicit relative `--include` paths. Do not infer that every file in a project is in scope.2122## Coordinate the six skills2324Follow this order when the relevant stage applies. A stage may be marked `not-applicable`; do not invent missing work to make it pass.2526| Stage | Owner | Required handoff |27| --- | --- | --- |28| Contribution and argument | `top-cs-writing` | claim IDs, evidence needs, manuscript plan |29| Literature evidence | `top-cs-evidence` | citation ledger and claim-to-source map linked to claim IDs |30| Figures | `top-cs-figure` | figure briefs linked to claims and evidence |31| Manuscript refinement | `top-cs-polishing` | terminology and revision notes |32| Pre-submission risk audit | `top-cs-reviewer` | review issues, threatened claims, proposed actions |33| Response and verified change | `top-cs-response` | revision IDs linked back to review issues |3435`top-cs-figure` is the only renderer. This workflow may request or validate a figure handoff, but never renders a figure itself.3637## Record only traceability3839Use `workflow-manifest.schema.yaml` and `references/handoff-and-checkpoints.md` as the project contract. Maintain stable IDs and links:4041```text42claim -> evidence -> figure43claim -> review issue -> revision44```4546Expected observations, planned figures, and unresolved reviewer issues are not completed results. Preserve those states explicitly.4748## Check status4950```text51python scripts/paper_workflow.py inventory --project <project-root> --include paper/main.tex52python scripts/paper_workflow.py status --project <project-root>53python scripts/paper_workflow.py status --project <project-root> --format json --strict54```5556Normal status output is advisory and exits successfully when the manifest is structurally valid. `--strict` exits non-zero for incomplete checkpoints, missing links, unverified evidence, or pending author confirmation. It does not claim that a paper is accepted or technically correct.5758## Boundaries5960- Do not fabricate experiments, figures, citations, reviewer comments, venue rules, or completion evidence.61- Keep all tracked paths project-relative and inside the chosen project root. Reject absolute paths, traversal, missing files, and escaping symlinks.62- Use current official venue sources through the specialist skills; a workflow status is not a policy source.63- Do not overwrite an existing manifest without the user's explicit `--force` request.6465## Resources6667- `scripts/paper_workflow.py`: initialize, inventory explicitly selected files, and inspect project traceability.68- `references/handoff-and-checkpoints.md`: checkpoint meanings and cross-skill handoff rules.69- `../_shared/contracts/workflow-manifest.schema.yaml`: public schema for the project state file.
zhiming33416