# Goal Mvp

> Use when the user writes /goal MVP, /goal mvp, Goal MVP, GoalMvp, $GoalMvp, $goal-mvp, or asks to turn a goal, idea, app concept, startup concept, game concept, automation, plugin, or Codex skill into a small buildable MVP. This skill runs a five-step workflow: clarify with mandatory questions, scope, plan, build, verify and launch.

- Skill: `kappaemme-git/goal-mvp` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add kappaemme-git/goal-mvp`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kappaemme-git/goal-mvp/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: kappaemme-git (https://skillmd.com/u/kappaemme-git)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kappaemme-git/goal-mvp

---


# GOAL MVP

Turn a raw goal into a working MVP with a bias toward shipping something testable in the current workspace.

## Core Rule

Do not start building on the first response unless the user explicitly asks to skip questions. First confirm the goal with a short clarification checkpoint, then convert the user's goal into concrete scope, build the smallest useful version, verify it, and hand off the result with a demo path or next action.

## First Response Rule

On the first response after this skill is triggered:

1. Restate the interpreted goal in one sentence.
2. Ask exactly 3 short clarifying questions.
3. Stop and wait for the user's answers.

Only skip this checkpoint if the user writes one of these explicit bypass phrases:

- "procedi senza domande"
- "no questions"
- "skip questions"
- "vai diretto al build"

If the user gives partial answers, make reasonable assumptions for the rest and continue to scope, plan, build, and verify.

## Five-Step Workflow

### 1. Clarify

Extract:

- target user
- problem or desire
- core outcome
- constraints, stack, deadline, or format
- success criteria

Ask exactly 3 short questions before build begins. Prefer questions that change product direction:

- Who is the target user?
- What is the one output the MVP must produce?
- What should be included or avoided in the first version?

After the user answers, summarize the assumptions in 2-4 bullets and continue.

### 2. Scope

Define the smallest useful MVP:

- one primary user journey
- 3-5 essential features
- explicit non-goals
- a demoable output

Prefer a narrow product that works over a broad plan. Cut dashboards, auth, payments, admin panels, AI agents, and integrations unless they are central to the goal or already present in the repo.

### 3. Plan

Choose an implementation path that fits the existing context:

- use the current repo stack when one exists
- for a new simple web MVP, prefer Vite/React or the repo's existing frontend setup
- for mobile MVPs, use Expo/React Native when available
- for games, include core loop, controls, scoring, fail/win state, and playtest
- for AI products, include model flow, prompt boundaries, failure cases, and cost awareness
- for skills/plugins, create valid Codex structure and validate it

Provide a short plan only when it improves coordination. Then execute.

### 4. Build

Implement the MVP end to end:

- create or edit the needed files
- keep changes scoped
- use existing patterns before introducing new abstractions
- include realistic sample data when external services are not required
- avoid fake buttons or dead-end controls in user-facing flows

If the goal is a content artifact rather than software, build the artifact directly: document, deck, spreadsheet, launch post, script, or prompt pack.

### 5. Verify And Launch

Run the relevant checks:

- build, tests, lint, or typecheck when available
- local smoke test for apps
- browser or screenshot verification for visual/front-end work
- validator scripts for Codex skills

Finish with:

- what was built
- how to run or view it
- verification performed
- next best improvements
- launch assets when relevant, such as README notes, pitch copy, demo prompt, or X post draft

## Invocation Patterns

Treat these as equivalent:

```text
/goal MVP build ...
$GoalMvp build ...
$goal-mvp build ...
Goal MVP: build ...
```

When the user says they want to "include /goal", explain only if needed: this skill does not patch Codex's native slash command system, but it is designed to trigger from `/goal MVP` text and explicit `$goal-mvp` invocation.

## Demo Prompt Template

Use this template when the user wants to test the skill in a video:

```text
/goal MVP crea una micro-SaaS per freelance web designer che trova attività locali senza sito, assegna uno score al lead e genera un messaggio outreach. Voglio una demo locale funzionante con UI curata, dati sample e CSV export.
```

## Social Launch Draft

When asked to prepare a launch post, draft concise Italian copy by default:

```text
Ho creato GOAL MVP: una skill Codex che trasforma "/goal MVP ..." in un workflow completo.

5 step:
1. chiarisce l'idea
2. taglia lo scope
3. pianifica l'MVP
4. builda davvero
5. verifica e prepara il lancio

La testo oggi con una demo: da idea grezza a MVP locale funzionante.
```