Menu
Use when writing an ideas report after brainstorming or when turning a chosen research direction into a proposal-style research plan
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when running the autoresearch loop for a project whose survey and validator gates have passed — executes batches of attempts (one git worktree + LOG.md each, scored only by the validator under a hard time limit), then reflects, reports, and re-plans; continues autonomously while authorized_rounds remain, otherwise stops for user review. Stage 4 of the autoresearch pipeline.
Use when setting the goal and building the validator for an autoresearch topic — defines the publishable bar with the user, splits dev instances from a sealed gitignored holdout, builds a Docker-canonical strict environment (recorded fallback allowed), implements the validate CLI with rich JSON errors, and passes the strictness self-test against negative controls. Owns the validator gate. Stage 3 of the autoresearch pipeline.
Use when building the evidence base for a chosen autoresearch topic — maps the insight areas needed to propose new ideas, downloads references to cover them via download-ref, distills each area into research/INSIGHTS.md for user selection, builds a structured domain database and pinned reference implementations, and catalogs all algorithms/software in research/CATALOG.md. Owns the survey gate. Stage 2 of the autoresearch pipeline.
Use when starting or resuming an autoresearch project — reads research/STATE.md to find the current stage of the pipeline (topics → db → validator → run), verifies the previous stage's gate artifacts exist on disk, and routes to the matching stage skill. Triggers on "start autoresearch", "resume autoresearch", "autoresearch status", "what stage is my research project at".
Use when choosing research topics within a domain that suit autoresearch and defining their score metrics — brainstorms candidates, scores each on machine-checkable success, cheap per-attempt evaluation, iteration headroom, and publishability, lets the user pick, then derives primary/guard metrics (with computation cost and gaming risks) for each chosen topic and writes everything to topics.md. Stage 1 of the autoresearch pipeline; invoked via the autoresearch dispatcher or directly with a domain.
Use when building a slide deck in Typst + Touying for a scientific talk, lecture, or project briefing — ships a browsable zoo of color themes, layout templates, and gadgets (callouts, theory boxes, CeTZ diagrams, pin annotations) that compose into projector-safe slides. Distinct from slide-writing (HTML, QudeLeap brand) and paper-writer (full manuscripts).
| name | idea-writer |
| description | Use when writing an ideas report after brainstorming or when turning a chosen research direction into a proposal-style research plan |
Write a structured ideas report after /brainstorm-ideas has converged on a research direction. For technology assessments use survey-writer; for manuscripts with real results use paper-writer.
Follow skills/_shared/writing-workflow.md for context loading, citation handling, gap-filling research, output format, diagrams, and finish checks.
docs/discussion/*-brainstorm-ideas-log.md; if multiple exist, ask which one to use./brainstorm-ideas first or describe the direction.articles/YYYY-MM-DD-<topic>-ideas-report.{md,typ,tex}.Draft each section, show, get feedback:
.bib fileWhen a concept is abstract or structural — a reduction between problems, a relationship between methods, a data flow, an architecture — draw a diagram instead of (or alongside) explaining it in prose. A picture makes the idea concrete and shareable in ways that paragraphs of text cannot.
Common diagram types:
Polya's "Looking Back": After drafting, review — can the result be derived differently? Can it be used for some other problem? Can you see the result at a glance?