Proposal Publish

Publishing is optional — a proposal markdown file is an acceptable hand-in on its own. Never pressure the user into installing anything; offer the paths and their costs.

Build

Run the build script (stdlib-only, ≥3.11):

python3 scripts/publish.py <proposal.md>            # PDF via best available engine
python3 scripts/publish.py <proposal.md> --handout  # stripped markdown export instead

The script resolves the best pipeline automatically: typst (preferred) → LaTeX engine → docx (last resort, no PDF), using the skill's templates/ (compact layout, RQ n: styling, citeproc). Outputs land next to the proposal; the script also ensures the workspace .gitignore covers build artifacts (shared rule: whichever skill first creates an ignorable artifact adds the entry).

When tools are missing

The script reports what is missing and what it would unlock. Guide concretely, best first: