메뉴
Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
Provides the shared STORM methodology, artifact layout, stage-gating contract, citation hygiene, and retrieval fallback. Use when executing any /storm:* skill (generate, research, outline, write, polish). Internal knowledge; never user-invocable.
Run the full STORM pipeline end-to-end. This skill should be used when the user asks to "generate a storm article", "write a wikipedia-style article about X", "research and write a long-form piece on X", or invokes /storm:generate. Orchestrates research -> outline -> write -> polish, skipping already-completed phases.
Run STORM phase 2 — outline generation. This skill should be used when the user asks to "generate an outline for a storm article", "draft a wikipedia-style outline", or invokes /storm:outline. Produces a draft outline from parametric knowledge then refines it using the research information table.
Run STORM phase 4 — article polishing. This skill should be used when the user asks to "polish the storm article", "finalize the article", or invokes /storm:polish. Adds a summary section, removes duplicate content, and verifies citation integrity.
Run STORM phase 1 — multi-perspective research. This skill should be used when the user asks to "research a topic for an article", "find sources on X from multiple perspectives", "do storm research on X", or invokes /storm:research. Discovers personas, runs simulated Q&A per persona in parallel, and produces an information table + deduplicated sources.
| name | storm-write |
| description | Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources. |
| user-invocable | true |
| argument-hint | <topic> [--retrieve-top-k N] [--output-dir PATH | --save] [--force] |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash(mktemp:*)","Bash(mkdir:*)","Bash(date:*)","Task","Skill"] |
Phase 3 of the STORM pipeline. Writes each outline section in parallel (one Task subagent per section), each grounded in top-k relevant sources from the research information table, with inline [n] citations.
storm-engine via the Skill tool.outline.md MUST exist (phase 2 complete). If absent, stop and instruct the user to run /storm:outline first.This phase is complete iff article.md exists and every outline section (except Introduction/Conclusion/Summary placeholders) has body text. If --force is not set and it exists, skip and exit early.
outline.md and research/sources.json. Index sources for retrieval (simple: rank by keyword/heading overlap with the section title).polish).--retrieve-top-k 3), the full outline for context.[n] citations mapping to sources.json ids.<!-- TODO: no source -->.article.md. Preserve the heading hierarchy from outline.md.run-config.json: phases.write = "completed", section count, any TODO-flagged sections.[n] where n is an existing id in sources.json. Never mint a new id here.[n] immediately after the claim it supports. Multi-source claims use [1][2].Report: number of sections written, number of citations used, list of sections flagged as TODO (no source), and the path to article.md.