launch
Use when deciding what must be completed, deferred, or removed before launch; audits MVP launch readiness, identifies true launch blockers, and cuts work that does not materially affect safe core user journeys.
- License 许可
- MIT
- 所属仓库
- amoai-tech/mdeai
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- launch
- description
- Use when deciding what must be completed, deferred, or removed before launch; audits MVP launch readiness, identifies true launch blockers, and cuts work that does not materially affect safe core user journeys.
02 资源文件 1
- 参考文档references/full-prompt.md2.2 KB
03 SKILL.md 正文
LAUNCH — MVP Readiness
Goal Identify the minimum remaining work required to launch safely and cut work that does not materially affect the core product.
1. Define launch journeys Use requirements/MVP/current truth to define the critical user journeys and observable success.
2. Verify current truth Check relevant:
- current main/open PRs
- Linear
- production deployment
- Supabase/schema/config
- external providers
- real workflow evidence
3. Classify work
- 🔴 MVP · Launch Blocker
- 🟡 MVP · Launch Supporting
- 🟢 MVP · Complete
- ⚪ MVP · Post-MVP
- ❌ MVP · Removed/Obsolete Ask:
If this fails, can a real user still safely complete the core production journey? Do not classify from Linear status alone.
4. Find real blockers Examples:
- broken critical journey
- auth/RLS/isolation failure
- duplicate transactions/retries
- payment/webhook failure
- unsafe data
- source/schema/config drift
- unrecoverable failure
- required mobile failure
- missing diagnostics
- synthetic-only production certification
5. Build the shortest critical path Order:
blocker → dependency → user journey → security/reliability → supporting quality Use full Linear names:
SAN-#### · Exact Linear Task Name Cut speculative infrastructure and polish that do not reduce launch risk.
6. Define proof Use:
focused → RLS/integration → browser/E2E → exact production journey
Output
Launch verdict Ready / Not ready / Conditional.
For remaining steps, checks, and examples, see full prompt.
04 同仓库更多 Skills
mde-pr-review-supabase
Use when reviewing MDE Supabase SQL, Auth and RLS changes in a pull request.
mde-pr-review-stripe
Use when reviewing MDE Stripe payments and webhooks changes in a pull request.
mde-pr-review-nextjs
Use when reviewing MDE Next.js App Router changes in a pull request.
mde-pr-review-mastra
Use when reviewing MDE Mastra agent, tool and workflow changes in a pull request.
mde-pr-review-maps
Use when reviewing MDE Google Maps and Places changes in a pull request.
mde-pr-review-copilotkit
Use when reviewing MDE CopilotKit and AG-UI changes in a pull request.