// Use when the user wants to turn an idea into a fully formed design or spec before writing any code or building anything. Triggers on requests to build a feature, create a component, add functionality, modify behavior, or any creative work that requires clarifying intent, requirements, and design first.
Use when the user asks for captions, emails, sales copy, launch copy, website copy, DMs, scripts, posts, content rewrites, or nurture sequences in a specific brand voice. Also use when the user says things like "write this in my voice", "make this sound like me", "rewrite this", "does this sound on-brand", "too formal", "too robotic", or any request where the output needs to match a specific tone, style, or personality. Also trigger when the user pastes their own draft and wants it improved or adjusted.
Use when the user wants to repurpose a draft, article, transcript, research dump, or outline into multiple platform-specific outputs across Substack, LinkedIn, Threads, Instagram carousel, and Substack Notes.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when the assistant needs to synthesize multiple rough inputs — messy notes, scattered emails, transcript excerpts, meeting context, or uploaded documents — into a concise executive briefing. Especially relevant for founder prep, leadership updates, weekly operating briefs, post-meeting readouts, launch status briefs, partnership updates, hiring or finance summaries, and any situation where conflicting or incomplete inputs must be turned into decision-ready output.
Use when the assistant needs to locate files, inspect folders, summarize drive contents, create or rename folders, move or delete files, manage sharing, detect inherited or external access, clean duplicates, or run organization workflows through connected Google Drive. Connector-first operator for searching, reading, organizing, sharing, auditing, and automating Drive files and folders.
Use when the assistant needs to search, inspect, summarize, create, update, restructure, or maintain Notion pages, databases, tasks, docs, wikis, project trackers, meeting notes, content calendars, or operating systems through the Notion connector. Trigger for requests involving Notion read/write workflows, database updates, page creation, workspace search, status reporting, documentation generation, task management, content planning, or converting messy context into Notion-ready structures.
| name | brainstorming |
| description | Use when the user wants to turn an idea into a fully formed design or spec before writing any code or building anything. Triggers on requests to build a feature, create a component, add functionality, modify behavior, or any creative work that requires clarifying intent, requirements, and design first. |
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
You MUST create a task for each of these items and complete them in order:
docs/plans/YYYY-MM-DD-<topic>-design.md and commitdigraph brainstorming {
"Explore project context" [shape=box];
"Ask clarifying questions" [shape=box];
"Propose 2-3 approaches" [shape=box];
"Present design sections" [shape=box];
"User approves design?" [shape=diamond];
"Write design doc" [shape=box];
"Proceed to implementation planning" [shape=doublecircle];
"Explore project context" -> "Ask clarifying questions";
"Ask clarifying questions" -> "Propose 2-3 approaches";
"Propose 2-3 approaches" -> "Present design sections";
"Present design sections" -> "User approves design?";
"User approves design?" -> "Present design sections" [label="no, revise"];
"User approves design?" -> "Write design doc" [label="yes"];
"Write design doc" -> "Proceed to implementation planning";
}
The terminal state is proceeding to implementation planning. Do NOT start writing code or scaffolding before this step is complete.
Understanding the idea:
Exploring approaches:
Presenting the design:
Documentation:
docs/plans/YYYY-MM-DD-<topic>-design.mdImplementation: