菜单
Launch an AI-native product and learn from the first customers. Use when a founder has an MVP or beta and needs positioning, ICP, first users, founder-led sales, pricing, onboarding, launch plan, customer feedback loops, or an AI-assisted operating system for early growth.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validate an AI-native startup idea before building. Use when a founder has a problem hypothesis, customer segment, early market thesis, or product idea and needs customer discovery, opportunity filtering, wedge selection, market mapping, risk identification, or an evidence plan before starting an MVP.
Scope and plan an AI-native MVP after the problem and customer are credible. Use when a founder needs MVP scope, product architecture, coding-agent workflow, evaluation loops, technical debt control, security review, build milestones, or a practical plan for shipping the first useful version.
Scale an AI-native startup after early traction. Use when a founder has users, revenue, pilots, retention signals, or market pull and needs repeatable GTM, metrics, hiring, fundraising narrative, operating cadence, AI-assisted workflows, infrastructure priorities, or bottleneck diagnosis.
Diagnose the current stage of an AI-native startup and route founders to the right stage skill. Use when a founder asks where to start, is unsure whether they are in Idea, MVP, Launch, or Scale, wants a stage assessment, wants a practical founder playbook workflow, or provides company context and asks what to do next.
| name | ai-native-launch-stage |
| description | Launch an AI-native product and learn from the first customers. Use when a founder has an MVP or beta and needs positioning, ICP, first users, founder-led sales, pricing, onboarding, launch plan, customer feedback loops, or an AI-assisted operating system for early growth. |
Help founders turn a working MVP into a focused launch motion that creates customers, feedback, revenue signals, and repeatable learning.
If the founder provides a structured brief, use these inputs:
Product/MVP status:
Ideal customer profile:
Positioning hypothesis:
Current users or pipeline:
Pricing hypothesis:
Onboarding flow:
Acquisition channel:
Feedback signals:
Desired output:
Do not require the founder to provide a full launch brief. If the request is vague, ask up to five questions first:
1. What product or MVP can users try now?
2. Who is the narrowest ideal customer for the first launch motion?
3. How are you currently reaching users or buyers?
4. What launch problem is most urgent: positioning, sales, pricing, onboarding, or feedback?
5. What evidence do you have from users, demos, pilots, or sales conversations?
After the user answers, choose the narrowest useful launch artifact and state assumptions. Ask follow-ups only if the launch audience or available product is still impossible to infer.
references/positioning.md to convert product capability into customer value.references/founder-led-sales.md to plan outreach, discovery, demos, follow-up, and close/learn loops.references/pricing-and-onboarding.md to design a simple offer and activation path.references/launch-operating-system.md to replace repetitive founder attention with AI-assisted workflows.Use generic AI roles:
The Launch stage is complete when:
Return the most useful artifact for the request: