菜单
Use when the user asks to finalize and hand back an existing design or implementation plan stored in FlickNote.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sp-complete-design |
| description | Use when the user asks to finalize and hand back an existing design or implementation plan stored in FlickNote. |
Finalize an existing FlickNote design or plan without starting review or implementation.
Read the full note and its structure:
flicknote detail flicknote detail --tree
The note must live in the orientation project. Move it there if needed.
Check:
Write fixes directly back with flicknote modify, replace, append, or section operations.
Search the repository, prior notes, or external sources for facts that do not require user judgment. Fold useful findings into the note.
Ask the user only for decisions that materially change scope, behavior, or trade-offs. Persist the answer in FlickNote before continuing.
Re-read the updated note from top to bottom. Confirm that:
Return:
Keep the summary under 200 words. Stop there. Do not invoke review, ttal go, goal-impl, or any other next phase.
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 a request needs collaborative exploration of intent, constraints, alternatives, or design before the direction is settled.
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.
