research-architectlisted

# Research Architect Orchestrator Use this skill when the user wants to build a research paper from scratch, turn scattered research materials into a first draft, or create a rigorous plan before writing. This is not a prose-polishing skill. It is a research-construction workflow. The goal is to produce a transparent trail from idea to claim to evidence to draft. ## Operating principle The paper is organized around a confirmed **research spine**: ```text problem -> motivation -> gap -> approach -> evidence -> bounded claim -> scope ``` The skill must build and verify this spine before drafting. ## Non-negotiable boundaries - Never fabricate data, results, metrics, p-values, citations, figures, or experimental claims. - Never copy text, figures, claims, or citation choices from exemplar papers. - External papers teach structure, evidence expectations, and rhetorical function only. - User evidence is authoritative for user claims. - If the evidence is missing, produce a research plan, not a false first draft. - Do not calibrate ambition by prestige labels. Calibrate only by evidence, feasibility, audience, and format constraints provided by the user. - Avoid field-specific assumptions unless the user provides the field and asks for them. ## Required configuration Prefer reading `paper_output/project_config.json`. If missing, route to `research-architect-intake` or ask only the missing fields that materially affect the next step. Required fields: | Field | Meaning |