القائمة
You MUST use this before any writing work - creating blog posts, technical documentation, reports, or any content. Explores topic intent, audience, and purpose before writing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Complete document writing workflow with four stages: brainstorming → planning → execution → review. Use when user wants to write articles, blog posts, technical docs, or any long-form content.
Executes approved article plan section by section with validation checkpoints. Batch writing mode with human review.
Multi-pass article review covering logic, evidence, flow, and polish. Systematic quality assurance before publication.
Fast iterative writing using fresh subagent per section with two-stage review. Alternative to batch execution.
Use when you have an approved topic brief. Creates detailed article outline with section structure, key points, word counts, and research needs before writing.
| name | brainstorming |
| description | You MUST use this before any writing work - creating blog posts, technical documentation, reports, or any content. Explores topic intent, audience, and purpose before writing. |
Help turn rough ideas into focused article briefs through natural collaborative dialogue.
Start by understanding what the user wants to write about, then ask questions one at a time to refine the concept. Once you understand the topic, present the brief and get user approval.
Do NOT invoke writing-article-plan, write any content, create any outline, or take any writing action until you have presented a topic brief and the user has approved it. This applies to EVERY writing project regardless of perceived simplicity.Every writing project goes through this process. A short blog post, a single-page doc, a quick update — all of them. "Simple" articles are where unclear messaging causes the most wasted effort. The brief can be short (a few sentences for truly simple pieces), but you MUST present it and get approval.
You MUST create a task for each of these items and complete them in order:
docs/writing/YYYY-MM-DD-<topic>-brief.md and commitdigraph brainstorming {
"Explore the topic" [shape=box];
"Ask clarifying questions" [shape=box];
"Identify core message" [shape=box];
"Present topic brief" [shape=box];
"User approves brief?" [shape=diamond];
"Write brief document" [shape=box];
"Invoke writing-article-plan" [shape=doublecircle];
"Explore the topic" -> "Ask clarifying questions";
"Ask clarifying questions" -> "Identify core message";
"Identify core message" -> "Present topic brief";
"Present topic brief" -> "User approves brief?";
"User approves brief?" -> "Present topic brief" [label="no, revise"];
"User approves brief?" -> "Write brief document" [label="yes"];
"Write brief document" -> "Invoke writing-article-plan";
}
The terminal state is invoking writing-article-plan. Do NOT invoke executing-article-plan or any other writing skill. The ONLY skill you invoke after brainstorming is writing-article-plan.
Understanding the topic:
Key questions to explore:
Presenting the brief:
Documentation:
docs/writing/YYYY-MM-DD-<topic>-brief.mdPlanning:
# [Topic] - Article Brief
**Date**: YYYY-MM-DD
## Audience
[Who will read this? Experience level, interests, pain points]
## Purpose
[What should readers gain? What action should they take?]
## Core Message
[The ONE sentence that captures your main point]
## Key Points
1. [Supporting argument/section 1]
2. [Supporting argument/section 2]
3. [Supporting argument/section 3]
## Tone & Style
[Formal/casual/technical/conversational - with examples]
## Constraints
- **Length**: [target word count]
- **Format**: [blog post/technical doc/report/guide]
- **Deadline**: [if applicable]
## References
[Any existing materials, sources, or inspiration]