From save-your-startup
Collaborative exercise to create a crystal-clear definition of "done" before any work begins. You describe the vision, the AI asks clarifying questions until both sides see the same picture.
npx claudepluginhub rickmanelius/skills --plugin save-your-startupThis skill uses the workspace's default tool permissions.
**From *Save Your Startup* by Rick Manelius (Chapter 10)**
Orchestrates design workflow from idea to docs: context gathering, clarification, brainstorming, design documentation, planning handoff. Use when starting any design process.
Turns vague requests like 'add a button' or 'fix the thing' into clear work briefs with scope, acceptance criteria, and stop conditions before planning or building.
Guides collaborative brainstorming to explore intent, clarify requirements, propose designs, and secure approval before implementing features or changes.
Share bugs, ideas, or general feedback.
From Save Your Startup by Rick Manelius (Chapter 10) Framework originated by Brene Brown, adapted for startup execution by Rick Manelius
"Five minutes spent here can save hours or days in Figma or a code editor."
Hand the same spec to 10 designers and you get 10 wildly different results. The gap between what the requester imagines and what the implementer builds is almost always larger than either side realizes. Painting done closes that gap before a single pixel moves or a single line of code ships.
You are Person A -- the one with the vision. I am Person B -- the one who will ask clarifying questions until I can see exactly what you see.
We will move through five phases together:
Tell me what "done" looks like in as much detail as you can. Don't worry about being perfect or exhaustive yet. Just paint the picture.
I will ask you:
Take your time. The more vivid, the better.
Once you've shared your initial vision, I will ask targeted questions to fill in gaps, surface assumptions, and sharpen the picture. Expect questions like:
I will keep asking until the picture is sharp enough that I could describe it back to you and you would say "yes, exactly."
As I ask questions, you fill in the blanks. It is okay to say "I don't know yet" or "I haven't thought about that." Those are some of the most valuable answers because they reveal assumptions that would otherwise become expensive surprises later.
When the picture feels complete, I will write back a clear summary of what "done" looks like. This summary will include:
You review the summary. If something is off, we adjust. We are done when you can read the summary and say: "If someone delivered exactly this, I would be thrilled."
Let's paint done. Tell me:
I will take it from there.
By the end, you will have a clear, shared definition of done that both of us agree on -- written down, specific enough to act on, and explicit enough that a third party could read it and build the right thing.