method-section-explainer
Method Section Explainer
Explain methods so reviewers can understand what is new, how it works, and why each design choice exists. This skill is for writing and structuring the method section, not inventing the algorithm.
Use this skill for:
- choosing method section structure
- introducing notation and problem setup
- writing method overview prose
- sequencing modules, losses, training/inference procedures, or system components
- deciding where algorithm boxes, equations, and overview figures belong
- explaining design rationales without overclaiming
- moving implementation details to appendix or experiment setup
Do not use this skill for designing a new algorithm. Use algorithm-design-planner for method design. Use paper-writing-assistant for broad prose. Use paper-writing-memory-manager to record notation, method terminology, overview-figure dependencies, and stale result/caption locations. Use figure-results-review for figure quality. Use paper-draft-consistency-editor after the section exists.
Skill Directory Layout
More from a-green-hand-jack/ml-research-skills
project-init
Initialize an ML research project control root. Use for paper/code/slides repos, shared memory, GitHub Project alignment, agent guidance, worktree policy, and lifecycle handoffs.
39init-python-project
Initialize or enhance a Python/ML project. Use for new repos or forks needing production structure, uv environment setup, and research evidence docs.
37new-workspace
Create Git branches or worktrees for research code and paper versions. Use for experiments, baselines, rebuttal fixes, arXiv/camera-ready branches, and worktree memory.
36project-sync
Sync verified code-side experiment results into paper memory. Use when logs, reports, run docs, or user-confirmed metrics should become paper-facing evidence.
36init-latex-project
Initialize a LaTeX academic paper project. Use for new conference or journal papers needing templates, macros, venue preambles, and writing guidance.
36add-git-tag
Create annotated Git milestone tags. Use when completing a phase, releasing a version, or marking a research checkpoint.
36