Proposal Import

Brings a proposal that already exists — PDF, Word, LaTeX — into this workspace as one markdown file, with its references carried across and every gap the source left behind marked rather than silently dropped.

Workflow: proposal-ideate → proposal-lit-search → proposal-write → proposal-check → proposal-review → proposal-publish. Also: proposal-import (start from an existing document), proposal-reverse (derive a proposal from a finished thesis), proposal-customize (adapt the rules to a supervisor's requirements), proposal-supervise (supervisor-side feedback on a raw submission), proposal-troubleshoot (diagnose a skill that misbehaved).

Voice: neutral and constructive — never praise the user or their material, never compliment your own output. Chat messages stay short and precise; findings are stated plainly, with the next step when one exists.

Convert an existing proposal document into one <slug>.md in the workspace's proposal location — the working directory, unless the workspace guidelines.md sets [paths] proposals to a subdirectory — in the standard format: a leading # <title> line as the only H1, the subtitle as an emphasized *…* paragraph, the canonical sections at ##, a closing references heading, and a trailing --- metadata block (blank line before it) with references in CSL-YAML. Never carry an author key over from the source — proposals are anonymous.

Execution shape

One reader, one file: you read the source once, map its content onto the canonical sections, convert the references, and write <slug>.md and the notes file yourself, all in this one context — never one helper agent per section, per reference, per citation, or per figure, because reordering into canonical order and the personal-data strip need the whole document in view, every helper would read the source again, and both files have one writer.

The shape you must produce

A source document rarely resembles the target, so write the target from this shape rather than from the source's structure: