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 evaluate competitors, understand the competitive landscape, or position their product against alternatives.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Activate when a founder needs to analyze the competitive landscape, evaluate specific competitors, find differentiation opportunities, or prepare a competitive brief. Trigger phrases include "who are our competitors," "analyze this competitor," "competitive landscape," "how do we compare to X," "feature comparison," "what's our moat," or "differentiation opportunities." Also activate before fundraising (investors will ask) or when entering a new market segment.
One paragraph defining the market structure: how many players, how fragmented, major categories of solutions, and overall market dynamics.
For each competitor:
| Dimension | Details |
|---|---|
| Company Profile | Background, founding, funding, team size, headquarters |
| Core Product Strengths | Key capabilities, UX quality, integrations, technical advantages |
| Product Gaps | Missing features, weak areas, customer complaints |
| Business Model & Pricing | Model type, price points, free tier, enterprise options |
| Competitive Threats | What makes them dangerous -- momentum, funding, distribution, brand |
market-research -- Pair competitive analysis with market sizing to understand both the landscape and the size of the prize.prd-writing -- Use competitive gaps to inform the solution section of a PRD. Build what competitors miss.user-research-synthesis -- Ground feature comparisons in what customers actually value, not what competitors assume they value.User: "I need a competitive landscape slide for our Series A deck."
Good output: A market overview paragraph, profiles of 4-5 key competitors highlighting their weaknesses relative to the startup's strengths, a differentiation map showing clear whitespace where the startup sits, and a positioning recommendation that tells a narrative about why competitive dynamics favor the startup's approach.
User: "We keep losing deals to Competitor X. Help us understand why and how to win."
Good output: Deep analysis of Competitor X's strengths in the dimensions that matter to buyers (e.g., enterprise readiness, integrations, brand trust), identification of the specific evaluation criteria where they win, and actionable recommendations to either match their advantages on must-have dimensions or shift the evaluation criteria to dimensions where you are stronger.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。