When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to plan or execute a product launch — including pre-launch content sequences, launch funnels, JV/affiliate launches, cart open/close strategy, or evergreen launch funnels.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Instead of one long sales letter, spread the sales message across 3-4 pieces of pre-launch content over 7-14 days. Each piece delivers value while building desire:
Give away your best material for free during pre-launch. When you deliver massive value before asking for the sale, you build reciprocity and prove competence. Do not hold back your best content out of fear — generosity in pre-launch drives sales at cart open.
| Phase | Timing | Activities |
|---|---|---|
| Pre-Pre-Launch | 4-6 weeks before | Seed the idea, build launch list, survey audience |
| PLC 1 | 10-14 days before | Release Opportunity content |
| PLC 2 | 7-10 days before | Release Transformation content |
| PLC 3 | 4-7 days before | Release Ownership content |
| PLC 4 / Cart Open | Launch day | Release Offer, open cart |
| Cart Open | Days 1-3 | Daily emails, testimonials, FAQ |
| Final Push | Days 4-5 | Multiple daily emails, urgency, countdown |
| Cart Close | Days 5-7 | Final call emails, cart closes (for real) |
| Post-Launch | Days 8-14 | Thank buyers, follow up non-buyers, debrief |
content-strategy — When the launch needs supporting content to sustain post-launch momentumsocial-content — When launch messaging needs to be adapted for social platformsemail-marketing — When the launch relies on email sequences for waitlist nurture and follow-uplanding-page — When the launch requires a dedicated sales page optimized for conversionExample 1: Online course launch
"I have a 5,000-person email list and a new course on data analytics. Help me plan the launch."
Good output: Recommend an internal launch with full PLC sequence. PLC 1 (10 days before): video on "The 3 Myths Holding Back Your Data Career." PLC 2 (7 days before): case study of a student who achieved a specific result. PLC 3 (4 days before): walkthrough of the course modules and ownership experience. Cart open for 5 days with a fast-action bonus (first 48 hours get a live Q&A session). Email sequence: 2 emails per PLC release, daily emails during cart open, 3 emails on cart close day. Target: $100-150K launch based on list size and typical conversion rates.
Example 2: SaaS product with seed launch
"We have a new SaaS tool and only 200 beta users. Should we do a big launch or start small?"
Good output: Recommend a seed launch first — offer the product to 50-100 beta users at founding member pricing to validate demand, collect testimonials, and refine the offer. Use their feedback to build PLC content for the internal launch 6-8 weeks later. Only consider a JV launch after the internal launch proves the funnel converts.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis. Also activate for "design the system", "how should I architect this", "monolith vs microservices", or architecture decision records.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".
日本語の概要は準備中です。原文の説明を表示しています。
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this". Also activate when reviewing a pull request or diff.
日本語の概要は準備中です。原文の説明を表示しています。