Menu
Use when a request needs collaborative exploration of intent, constraints, alternatives, or design before the direction is settled.
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
Refresh context window — agent writes handoff and restarts
CLI image manipulation — convert PNG/JPG to SVG, remove watermarks, resize, crop, and edit raster images using ImageMagick and vtracer
Triage plan review findings — categorize issues, fix actionable ones, report
Use when the user asks to finalize and hand back an existing design or implementation plan stored in FlickNote.
Use when a bug needs root-cause diagnosis and a written fix plan before implementation.
Use when the user asks for a concrete implementation plan for an agreed change before code is written.
| name | sp-brainstorming |
| description | Use when a request needs collaborative exploration of intent, constraints, alternatives, or design before the direction is settled. |
Turn an unclear idea into an agreed design through conversation. This skill ends when the design is recorded; it never starts planning or implementation.
After the user approves the direction, save the agreed design to the orientation project:
flicknote add --project orientation
The note should contain:
Return the FlickNote ID and a short summary. Stop there. Do not invoke or recommend another skill automatically.
For a small or mechanical change where the conversation itself is enough, skip the note and state the agreed direction.
