Menu
Start shaping a new business idea. Use when starting from scratch or when the user says "shaper", "shape this idea", or "help me form a business."
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
| name | shaper:kickoff |
| description | Start shaping a new business idea. Use when starting from scratch or when the user says "shaper", "shape this idea", or "help me form a business." |
Captures the initial spark of an idea and sets up the Shaper's internal state. It is very fast and leads directly into the Lean Canvas.
Before running this command, read ../../references/shared-protocols.md.
shaper:kickoff.If .shaper/business_state.md already exists:
AskUserQuestion tool to ask: "What would you like to do?" with these single-select options:
/shaper:help).Ask: "What is the core idea you want to explore? (e.g., 'Airbnb for dogs' or 'A better CRM for mechanics')"
Wait for response.
Use the AskUserQuestion tool to ask: "How do you like to work with me?" with these single-select options:
Create .shaper/business_state.md in the project root.
## Business State Initialized
- **Idea**: [Summary of the idea]
- **Working preference**: [Thorough / Balanced / Fast]
### Suggested Next Step
→ `/shaper:canvas` — Let's map out the 9 blocks of your Lean Canvas to see if this is viable.
→ `/shaper:help` — See all available commands.
.shaper/business_state.md using the schema defined in ../../references/shared-protocols.md (Section 7). Populate Profile fields (idea, working_preference, initialized_date). Leave all other sections empty.Design project structure and record technical decisions. Use when the user says "architect", after product exploration is complete, or when revisiting architecture after a pivot. Does NOT generate source code — that is build's job.
Generate code from the architecture plan. Use when the user says "build", after architect has recorded a plan, or when re-generating after an architecture change. This is the only command that writes source code.
Design the solution interface (UX/UI, API contract, or agent system). Use when transitioning from the product brief to the engineering phase to determine how the product behaves and looks.
Interactive product discovery — what are we building, who is it for, and what does v1 look like. Use when starting product exploration, adding a new feature, revisiting scope or requirements, or when the user says "discover".
Context-aware command menu showing all available maker commands with recommendations based on current project state. Use when the user says "help", asks how to use maker, asks where to start, asks what maker does, or seems unsure what to do next.
Initialize project context and preferences. Use when starting a new project, when the user says "kickoff", or when there is no .maker/project_state.md and the user wants to get started.