'mvp' 검색 결과

기능 추가와 버그 수정 등 개발 작업을 변경 규모에 따라 조사·계획·테스트·검토 단계로 배분합니다. 관련 스킬이 공유하는 절차에 계획 승인과 커밋 전 확인을 포함합니다.

• 기능 추가와 버그 수정 절차를 통일합니다
• 변경 규모에 맞는 단계를 선택합니다
• 설계 문서에서 MVP 개발을 진행합니다

Turn a design or requirements document into a working MVP, a minimal product, through small end-to-end feature slices. It coordinates scaffolding, repeated generation and evaluation, reviews, and approval gates, with separate commits for the scaffold and each slice.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a working MVP from a design document
• Planning small end-to-end feature slices
• Scaffolding the first working feature

Plan a small SaaS business, from checking demand to launching an initial product. The skill helps define an MVP, a first version with only essential features, choose pricing, organize launch tasks, and consider customer acquisition and retention.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking demand before building a SaaS product
• Scoping an MVP around one core feature
• Setting subscription prices and pricing tiers

Plan an existing development phase around a small, usable feature. Define who needs it and why, check whether the work should be split, update ROADMAP.md, and hand off to phase planning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reframe an existing phase around a minimum usable feature
• Clarify the user, desired action, and purpose
• Split an oversized story into multiple phases

Review a product or major feature before development starts. Assess demand, revenue, repeat use, trust, and user reach, then identify the riskiest assumption, a small validation step, and work to delay.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check demand and revenue assumptions before building an MVP
• Review positioning before creating a landing page
• Assess adoption risk for a major feature

社内向け業務アプリを「業務に必要な機能一式を盛り込んだ初回リリースを最短で出し、そこから育てる」MVPファーストで開発するための思考法・進行ルール。依頼者が非エンジニアである前提の会話プロトコル、1画面1目的のUI原則、決めること/決めなくていいことの仕分け、社内アプリの必要最低限セキュリティライン、残課題の管理方法を定める。「とりあえず形にして」「まず動くものを」「MVPで」「さっと使えるものを」「社内ツールを早く」「非エンジニアに見せたい」などの依頼で必ず使用する。新規アプリの要件定義ステージ開始時に app-excellence とセットでロードする。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Define the smallest viable experiment and MVP for a selected one-person company opportunity. Use when Codex needs to explain what MVP means when needed, verify prerequisites, ask one question at a time, present multiple MVP options, and write user-confirmed outputs into `opc-doc/`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MVP 开发专家团主理人（郝交付 · 交付总监）。统筹 7 位专家（PM/设计/架构/前端/后端/QA/运维）按 6 阶段 SOP 完成 MVP 产品交付。 触发词："帮我做个产品"、"MVP 开发"、"快速搭一个"、"做个 demo"、"从零搭建"、"做一个 XX 应用"、"帮我开发 XX"。 路由逻辑：综合性产品开发任务走完整 SOP；单一维度需求（仅设计/仅后端/仅部署）可直调对应专家。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find the ECC command sequence for a development task, including the order to run commands and when to stop. It reads current command files, groups related workflows, and provides guidance without executing them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding the command sequence for a bug fix
• Choosing commands for building an MVP
• Browsing available ECC workflow groups

Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

Plan the MVP build from a PRD and an MVP scope, as a full development plan or an ultra-lean build spec, with the AI Product Development Toolkit's planning prompts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Chains /mvp → /spec — analyzes an app from video/screenshots/description, then generates implementation stories. Triggers: analyze and spec, product analysis to stories, app teardown to specs, full analysis pipeline, mvp to spec.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn a rough idea into a concrete concept through guided discussion. Explore alternatives, compare user value and feasibility, and produce a Markdown brief covering the recommended direction, assumptions to test, minimum scope, and explicit exclusions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Shaping a vague product or feature idea
• Exploring alternatives before choosing a direction
• Testing assumptions before committing to a plan

Coordinate multiple skills to deliver a SaaS prototype, audit web security, build an AI agent, test browser behavior, or design a domain model. Verify each step before continuing and report completed work with supporting evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Delivering a SaaS minimum viable product
• Running a web application security audit
• Building an AI agent system with checkpoints

Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find documented features missing from the implementation
• Prioritize gaps in core product functionality
• Turn feature gaps into actionable GitHub issues

Turn a product idea into a Lean Canvas, a nine-part outline of business assumptions. Define customer problems, solutions, value, channels, revenue, costs, and metrics, then identify risky assumptions and suggest experiments to test them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organizing business assumptions for a new venture
• Clarifying target customers and the value offered
• Reviewing revenue, costs, and key metrics together

Structure problem solving around clear goals, competing explanations, experiments, and measurable results. Use the cycle to diagnose bugs, validate features, compare prompts, or evaluate an early product, then choose the next step based on evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Diagnosing a bug with a quick investigation
• Comparing prompt structures through experiments
• Defining success criteria for a feature

星火燎原：从零起步、资源极少时，先评估客观条件，选定一个能站稳、能复用、能扩展的"根据地"（最小切入点），扎根后再逐步扩张，拒绝四处出击的流寇主义。当启动新项目、做 MVP / pilot、面对宏大目标不知从何下手、或做了很多零散事却没有积累时触发；项目已有稳固基础、只是修改现有系统时不触发。 English: Spark a prairie fire. When starting from almost nothing, assess the conditions, choose one base area (a minimal foothold that can hold, be reused, and expand), dig in, then grow step by step instead of scattering effort. Trigger for new projects, MVPs, pilots, daunting goals with no obvious first step, or busy work that accumulates nothing; skip when a solid base already exists or the task modifies an existing system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", "minimum viable experiment", "should we pivot", "test a business idea cheaply", or "build the smallest version first". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change direction on a product bet. Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build the actual product — from landing page to deployed MVP with payment integration, QA testing, and post-deploy canary monitoring. Handles code generation, deployment, database setup, authentication, Stripe/payment integration, systematic QA protocol, and production health scoring. Use when the user needs to build something, deploy a product, set up payments, create a landing page, or says 'build this', 'deploy', 'create MVP', 'set up payments', or 'ship it'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Discover and validate product ideas, analyze markets, scope MVPs, and optimize app store presence for iOS/macOS apps. Use when user asks to discover, validate, assess, scope, or analyze product ideas, market opportunities, or when they mention "product agent", "app idea validation", "should I build this", "MVP", "market analysis", or "ASO".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty. Use when iterating toward product/market fit, designing MVPs, deciding whether to pivot or persevere, setting up actionable metrics, or accelerating the Build-Measure-Learn loop. Triggers include 'how do we test this idea fast', 'what should our MVP look like', 'our metrics look good but we're not growing', 'should we pivot', 'we're building features no one uses', 'how do we measure validated learning', 'vanity metrics vs real metrics', 'how to do innovation accounting'. NOT for companies with proven product/market fit scaling a known playbook (use Crossing the Chasm), not for determining Market Type (use Four Steps), not for sales methodology (use SPIN Selling), not for pricing strategy (use Monetizing Innovation).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.