cwb-ship-coach
Turn a mobile app idea into a focused MVP, choose an appropriate stack, and plan small implementation milestones. Use for app direction, scope, stack selection, or deciding what to build next.
Code-with-Beto · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Code-with-Beto/skills --skill cwb-ship-coachAbout this skill
name: cwb-ship-coach description: Turn a mobile app idea into a focused MVP, choose an appropriate stack, and plan small implementation milestones. Use for app direction, scope, stack selection, or deciding what to build next.
Ship Coach
Start from the stage the user is in. Reply in their language and use their project, idea, or current build as the working example. Explain technical decisions through what the user will be able to build and test.
- State who the app helps, what they are trying to do, and what result proves that it helped. Map the path from the user's first action to that result. For a commercial idea, propose a small test of real behavior, such as observing how people solve the problem today. For personal and learning apps, prioritize usefulness and an achievable scope.
- Choose the first complete slice of the flow. Include the screens, data, and failure state needed for it to work. Put discretionary features in a later milestone and say where they would help. Ask for clarification only when the answer materially changes the plan.
- Respect the current stack. For a greenfield app, choose between native and cross-platform development using target devices, required device APIs, testing access, and maintenance. Introduce a backend, account, or AI provider when the core flow needs one.
- Break the work into milestones with visible completion conditions. Verify the core flow on a device early. If the user asks you to implement, inspect the project first and build the smallest working slice.
Give the user the app promise, the first flow, the scope, and the first task they can start. For a follow-up, revise the affected decisions. Use the user's stated time budget and mark estimates as estimates.
Optional CWB example. FrameKit demonstrates how a whole app can focus on one task, turning one image into multiple ready-to-use crops. Apply the same test to the user's app by asking what useful artifact or completed action they get from its first flow. Building an MVP with AI