manji-standard-paper-writing

Orchestrator skill for the Abstract section - delegates writing to the abstract subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing or revising an abstract for an academic paper (international conference full paper, journal article, workshop paper). Triggers include mentions of "abstract", "アブスト", "要旨", "要約", requests to "write/revise/fix the abstract", or when the user shares an abstract draft for review. Also trigger when the user is finalizing a paper and needs the abstract aligned with the rest of the manuscript. This skill enforces a 5-part structure that leads with the technical contribution (NOT the user study details) and keeps contributions structurally clear (numbered list OR prose enumeration — both are acceptable).

Orchestrator skill for the Conclusion section - delegates writing to the conclusion subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing or revising the Conclusion section of a paper. Triggers include "Conclusion", "結論", "まとめ", "締め", "最終章", or when the user says "the paper is almost done, just need to write the conclusion". This skill ensures the conclusion does three things in order: (1) briefly restate the problem and approach, (2) summarize key findings in relation to the hypotheses, (3) gesture toward broader implications. It should be concise (typically 2-4 paragraphs) and must align with the Abstract and Contributions bullet list in the Introduction.

Orchestrator skill for the Discussion section - delegates writing to the discussion subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing or revising the Discussion section of a paper — the section that interprets the Results, explains underlying mechanisms, and connects findings to prior work. Triggers include "Discussion", "考察", "6章", "interpret results", "mechanism", or when the user is explaining *why* their results came out a particular way. Critically, this skill enforces precise interpretation of cited works (checking whether a prior study is truly contrasted or actually consistent with the current findings) and separates mechanistic explanation from the descriptive Results section. Also use this skill when explaining interaction effects, lack-of-interaction findings, or reconciling findings with or against prior literatur

Orchestrator skill for the Introduction section - delegates writing to the introduction subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing or revising the Introduction section of an academic paper. Triggers include "write the intro", "イントロを書く", "introduction を直す", "第1章", "Heilmeier", requests to review intro drafts, or when a user explicitly says the abstract is done and they want to move to the introduction. This skill enforces the Heilmeier's Catechism structure (4 paragraphs corresponding to questions 1-4), and critically, requires Contributions at the end as a bulleted list (not Research Questions). Readers want to know conclusions, not questions — so the intro ends with what was found, not what was asked.

Orchestrator skill for the Limitations section - delegates writing to the limitations subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing or revising the Limitations, Limitations and Future Work, or Future Directions section of a paper. Triggers include "Limitations", "Future Work", "limitations", "将来研究", "今後の課題", "制約", "将来の方向性". Also trigger when a reviewer asks the authors to "discuss generalizability" or "address sample limitations". This skill helps the user acknowledge limitations honestly (avoiding both over-apology and hiding weaknesses) and frame them as motivated future directions rather than pure weaknesses.

Orchestrator skill for the Method / System / Experimental Setup section - delegates writing to the method subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing the Method, System, Experimental Setup, Apparatus, or Implementation section of a paper — the chapter that describes the technical system or platform built before running the user study. Triggers include "Method", "Experimental Setup", "System", "実装", "手法", "システム概要", "装置", "3章", or "setup". This section should justify design decisions (not merely describe them), explicitly link the system design back to the research gap from the Introduction, and set up the independent variables that the subsequent user study will manipulate.

Paper-writing pipeline manager (a.k.a. paper-write-orchestrator / paper-write-manager). Use when the user wants the MSPW agent team to write, extend, revise, or review an academic manuscript — triggers include "論文を進めて", "〜章を書いて/直して", "レビューして反映して", "specを実装して", "/paper-orchestrator". Orchestrates the section-writer subagents (abstract … conclusion), paper-researcher, paper-reviewer1/2 and the writing-principles checker via the Agent tool, relays ALL inter-agent communication, and batches judgment calls to the user via AskUserQuestion. The orchestrator itself never writes manuscript prose, never reviews content, and never answers research questions from memory.

Spec-writing pipeline manager for paper changes. Use BEFORE editing the manuscript when a change deserves a design document — restructuring sections, changing claims/contributions, adding analyses/experiments, major revisions, reviewer-response plans. Triggers include "specを作って", "設計書", "変更計画", "リバイズ方針をまとめて", "/paper-spec-orchestrator". Produces docs/spec/NNNN-<slug>.md via the paper-spec-writer subagent, resolves unknowns via paper-researcher, and gets the spec approved by the user via AskUserQuestion. Never edits the manuscript itself; implementation is handed off to /paper-orchestrator.

Orchestrator skill for the Related Work section - delegates writing to the related-work subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing, revising, or restructuring the Related Work (related research) section of an academic paper. Triggers include "related work", "関連研究", "先行研究", "第2章", "2章を書く", requests to reorganize subsections, or when a reviewer/advisor points out that "it's unclear what perspective the paper takes" or "subsection structure is confusing". This skill requires (a) opening each Related Work section with a headline sentence that makes the organizing perspective explicit, (b) matching subsection titles to the actual content scope (not narrower, not broader), and (c) making the research gap crystal clear at the end of the section.

Orchestrator skill for the Results section - delegates writing to the results subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing, formatting, or revising the Results section of a paper. Triggers include "Results", "結果", "5章", "result section", or any context involving ANOVA tables, post-hoc tables, p-values, effect sizes, or Likert-scale boxplots. Also trigger when the user is preparing results for camera-ready submission and needs to double-check that hypotheses stated in the Study Design section are each explicitly judged as supported/partially supported/not supported. This skill enforces: (a) one paragraph per dependent measure, (b) explicit reference to each hypothesis, (c) strict separation of facts (Results) from interpretation (Discussion).

Orchestrator skill for the User Study section - delegates writing to the user-study subagent (this file is the rulebook the subagent loads at startup), routes open questions to paper-researcher and reviews to paper-reviewer1/2; the main conversation never writes prose itself. Use this skill whenever the user is writing, revising, or checking the User Study, Experiment, Evaluation, or Participant section of a paper. Triggers include "user study", "実験", "被験者実験", "evaluation", "experiment", "participants", "仮説", "hypothesis", "study design", "procedure", "measures", or "第4章". Also trigger when the user mentions standardized questionnaires, within-subjects, between-subjects, counterbalancing, or Latin Square. This skill enforces the standard HCI user-study structure (Participants / Study Design + Hypotheses / Measures / Procedure / Analysis) and requires explicit grounding of each hypothesis in prior work.