stage-proj-adopt

Migrate existing LaTeX manuscripts into the STAGE project layout with confirmed move plans.

2|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/wanghao9610/STAGE --skill stage-proj-adopt-wanghao9610
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stage-proj-adopt
Source: https://github.com/wanghao9610/STAGE/tree/main/.qwen/skills/stage-proj-adopt
Command: npx skills add https://github.com/wanghao9610/STAGE --skill stage-proj-adopt-wanghao9610

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bringing an already-started LaTeX paper, thesis chapter, or Overleaf export into a structured writing toolchain usually means manual reorganization, broken \input and \bibliography paths, and untracked numbers in the prose. This Skill inventories the draft read-only, confirms a mapping and per-file move plan before touching anything, and lands the manuscript in the STAGE layout without losing a line. ## Core Features & Use Cases - Read-only inventory and confirmed migration: Maps the main file, section inputs, figures, tables, bibliographies, styles, venue signals, and git history, then requires approval of the mapping and the per-file move plan before any file moves. - Path repair and build verification: Rewrites every \input, \graphicspath, and \bibliography edit named in the plan, then verifies the adopted tree compiles out-of-tree via latexmk. - Unsourced-claims backlog and evidence routing: Records every number already in the prose as an unsourced claim for the claims auditor, and routes candidate evidence files to the evidence curator without writing into the evidence store. - Use Case: You have an Overleaf export of a half-written paper. Run the adoption command with its path; the draft is copied into manus/, its references keep resolving, the build is verified, and every pre-existing result number is logged as an unsourced claim. ## Quick Start Run /stage-proj-adopt with the path to your existing LaTeX draft directory to inventory it, approve the move plan, and adopt it into the STAGE layout.

Frequently Asked Questions about stage-proj-adopt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate an existing LaTeX paper into a structured project layout?

Run the adoption command with the path to your draft directory. The skill inventories the manuscript read-only, proposes a per-file move plan into manus/ subdirectories, and executes only the rows you approve, then verifies the tree still builds.

How to import an Overleaf export into STAGE without breaking references?

Pass the Overleaf export directory as the source path. Files are copied in while the source tree stays untouched, and every \input, \graphicspath, and \bibliography edit forced by the move is named in the plan before being applied.

Does adopting a draft modify or delete my original files?

No. External source trees are only copied from, never modified. Inside the repository nothing is deleted, moves in a git tree use git mv to preserve history, and only untouched template placeholders may be overwritten.

What happens to result numbers already written in my draft?

Every number presented as a result is recorded verbatim with its file and line as an unsourced claim in the adoption record. The claims auditor later ingests this backlog and links each claim to registered evidence.

Can I adopt a draft if the build was already broken before migration?

Yes. Failures caused by paths the skill rewrote are fixed and re-run, but pre-existing breakage is reported with file and line and left to the owner rather than silently patched.