outline
Design paper structure: generate a section-by-section outline with purpose, key content, estimated length, and narrative arc. Adapts to paper type and venue conventions. Updates .papermill/state.md.
- License 许可
- MIT
- 最近更新
- 2026-10-23
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- outline
- description
- Design paper structure: generate a section-by-section outline with purpose, key content, estimated length, and narrative arc. Adapts to paper type and venue conventions. Updates .papermill/state.md.
03 SKILL.md 正文
Paper Outline
Help the researcher design the structure of their paper. A good outline is the skeleton that determines whether the paper's argument flows logically. Produce a section-by-section plan that is specific to this paper, not a generic template.
Step 1: Read Context
Read .papermill/state.md (Read tool) for:
- Thesis: The central claim and novelty (critical: the outline serves the thesis).
- Prior art: Key references and gaps (these shape the related work section).
- Format:
latex,markdown, orrmarkdown(affects section conventions). - Stage: Current progress.
- Venue: Target venue (affects length, section naming, and emphasis).
If .papermill/state.md does not exist, outlining can still proceed: ask the user to describe the thesis and intended contribution type directly. Suggest running /papermill:init afterward to persist the outline.
Also scan existing paper files (Glob/Read tools). If there is already a partial draft, read it to understand what exists.
Step 2: Determine the Paper Type
Different paper types have different conventional structures. Identify which applies:
- Theoretical/mathematical: Introduction, Preliminaries, Main Results, Proofs, Discussion, Conclusion
- Empirical/experimental: Introduction, Related Work, Method, Experiments, Results, Discussion, Conclusion
- Systems/engineering: Introduction, Background, Design, Implementation, Evaluation, Related Work, Conclusion
- Survey/tutorial: Introduction, Taxonomy/Framework, Section per topic, Discussion, Open Problems
- Short paper/workshop: Compressed: Introduction, Approach, Results, Conclusion
Ask the user if you are unsure. The structure should match the contribution type.
Step 3: Draft the Outline
For each section, specify:
| Field | Description |
|---|---|
| Section title | The heading as it will appear in the paper |
| Purpose | What this section accomplishes for the reader (1 sentence) |
| Key content | Bullet points of what goes here (3-5 items) |
| Estimated length | Approximate page/paragraph count |
| Dependencies | What must be established before this section |
Example:
3. Preliminaries
Purpose: Establish notation and recall the key definitions the reader needs. Key content:
- Series system model (Definition 2.1)
- Masked failure time observation model
- Exponential lifetime assumption and its implications
- Notation table for symbols used throughout
Estimated length: 1.5 pages Dependencies: None (self-contained background)
Step 4: Check the Narrative Arc
After drafting the outline, verify the story:
- Does the introduction motivate the problem clearly? The reader should understand why this matters by the end of the first page.
- Does related work position the contribution? It should make clear what gap this paper fills.
- Does the technical content flow logically? Each section should build on the previous one.
- Does the paper deliver on the thesis? The main results section should directly address the claim.
- Does the conclusion do more than summarize? It should state implications and future work.
Raise any structural issues with the user. Common problems:
- Related work that reads like a list rather than a narrative
- Main results section that is too dense with no intuition
- Missing "so what?" in the conclusion
- Sections that could be merged or reordered for better flow
Step 5: Present and Iterate
Present the complete outline to the user. Ask:
Does this structure capture the argument you want to make? Would you reorder, merge, or split any sections?
Iterate until the user approves.
Step 6: Update State File
Once approved, update .papermill/state.md (Edit tool). If .papermill/state.md does not exist, skip this step and suggest /papermill:init. Updates:
- Advance
stagetooutliningif it is earlier in the stage enum (never move it backward). - Write the outline to the markdown body under a
## Outlineheading (replace an existing## Outlinesection rather than adding a second one).
Append a timestamped note documenting the outline creation.
Step 7: Suggest Next Steps
Based on what the outline reveals, suggest the most relevant next step:
- If the outline exposed that the thesis is unclear or too broad → "The outlining process suggests the thesis may need sharpening. Consider running
/papermill:thesisto refine the claim before drafting." - If the outline includes a related work section with few references →
/papermill:prior-art - If the outline includes experiment/simulation sections →
/papermill:experimentor/papermill:simulation - If the outline includes proof sections →
/papermill:proof - Otherwise → "Begin writing with the section you feel most confident about. Many authors start with the method/results, not the introduction."
04 同仓库更多 Skills
worldsmith-methodology
Use when working in a project with a worldbuilding documentation ecosystem (docs/ or lore/ directory). Provides the documentation-first methodology: canonical hierarchy, doc roles (timeline, lore, characters, systems), propagation discipline, and the dual canonical and exploratory workflow.
prose-craft
Use when writing fiction, editing fiction prose, reviewing chapters, or drafting scenes. Covers prose craft, dialogue mechanics, scene structure, and common failure modes in AI-assisted fiction. Trigger phrases: "write fiction", "edit chapter", "prose review", "scene draft", "dialogue check", "fiction craft", "edit this scene", "review my prose".
vista
This skill should be used when the user asks about research directions, open problems, future work, or follow-up research from the academic literature. Trigger phrases include "open problems in X", "what's next for Y", "future work for paper Z", "research directions on T", "salient follow-up research", "what should I work on next in", "find me follow-up research unrelated to my prior work", "broad survey of W", "neglected directions in V". Routes the request to the right Vista MCP tool, reads back the structured paper sections, and synthesizes research directions in the conversation.
synthesize
Make a research-agent run conclude and write synthesis.md (outcome, key findings, failed approaches, open questions, recommendations). Signals a live researcher to wrap up, or launches one in synthesis mode when none is running. Use when results are good enough or the agent is stalling.
status
Show the current state of a research-agent run from .research/: liveness, cycles and budget, sub-problem and hypothesis statuses, eval trend, current focus, and branches. Read-only.
resume
Resume an interrupted research-agent run from .research/. Re-launches the researcher to reload its structured state and continue from the current focus, optionally on a named branch or with a new budget. Use after a session restart, crash, or explicit pause.