top-cs-paper-workflowlisted

# 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 1. Ask for the paper project root. Never search the home directory, cloud folders, or other projects. 2. Initialize the project-local state only after the user has chosen that root: ```text python scripts/paper_workflow.py init --project <project-root> ``` 3. 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. 4. 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 actio