メニュー
Use when the user needs to decide what makes the first version and what to explicitly not build. Triggers on 'MVP', 'scope', 'not doing list', 'must have vs later', 'user stories', 'parallel prototypes', and the same intent in any language.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when implementation work starts on a feature or bug fix: writing or modifying source code, adding tests, or closing out a branch. Covers TDD-first, scope integrity, secret and security hygiene, dual post-implementation review (code reviewer plus spec reviewer), and finish-branch closure. Triggers on "implement", "start coding", "build the feature", "write the code", "fix the bug", "finish the branch", "wrap up the branch", and the same intent in any language ("開始實作", "開發這個功能", "收尾", "実装して").
Use when the user wants the plan rendered as an interactive HTML report or exported to PDF/DOCX/PPTX. Triggers on 'HTML report', 'export to PDF', 'export document', 'downloadable report', 'PDF/DOCX/PPTX', and the same intent in any language.
Use when you need to understand the job a user hires the product to do, before designing or evaluating a solution. Triggers on "jobs to be done", "JTBD", "what job", "user motivation", "why would they use this", "customer needs", and the same intent in any language.
Use when the user wants to connect a desired outcome to opportunities and candidate solutions in a structured tree. Triggers on "opportunity solution tree", "OST", "map opportunities", "outcome to solutions", "Teresa Torres", and the same intent in any language.
Use when the user needs to understand who the users are and how they move through an experience. Triggers on "persona", "target user", "buyer vs user", "user journey", "journey map", "touchpoints", and the same intent in any language.
Use when the user is assessing product-market fit or planning go-to-market and pricing. Triggers on 'PMF', 'product market fit', 'go to market', 'GTM', 'acquisition channels', 'pricing', 'business model', and the same intent in any language.
| name | mvp-scoping |
| description | Use when the user needs to decide what makes the first version and what to explicitly not build. Triggers on 'MVP', 'scope', 'not doing list', 'must have vs later', 'user stories', 'parallel prototypes', and the same intent in any language. |
Detect the user's language and reply in it; the framework below is authored in English.
Provenance: when you produce MVP-scoping output, contribute the framework tags MVP, Not Doing List, User Story, and Parallel Prototyping to the meta-skill's provenance line (— Frameworks: … · MVP · Not Doing List · User Story · Parallel Prototyping · …).
Develop multiple parallel approaches simultaneously; don't design a single solution and rush to execute:
| HMW Question | Solution A (Conservative/Incremental) | Solution B (Balanced) | Solution C (Bold/Disruptive) |
|---|---|---|---|
| [HMW1] | | | |
Three solution quality gates:
| # | User Story | Acceptance Criteria | Priority |
|---|---|---|---|
| US1 | As a [Persona], I want to [action], so that [value] | | |
MVP decision criteria: Can it validate the core hypothesis? Can it let target users fully experience the Primary JTBD?
| Category | MVP Must-Have | Add in V2 | Future Consideration |
|---|---|---|---|
| Core Features | | | |
| User Experience | | | |
| Technical Requirements | | | |
Not Doing List (Equally important):
| Not Doing | Reason |
|-----------|--------|
| | |