- Home
- Skills
- Business & Operations
- MBTI Virtual Company – 16-Persona Product Review
Works with the AI Agents you already use
MBTI Virtual Company – 16-Persona Product Review
Simulate a 16-persona MBTI virtual company to audit product ideas, strategies, and technical decisions.
Free
MBTI Virtual Company – 16-Persona Product Review
Example session with this skill installed
Review this idea: a Pomodoro timer SaaS for developers at $9/month. It integrates with GitHub and Slack, auto-sets your Slack status to "focusing" and blocks notifications during a session.
- Read your context and instructions
- Compiled the mbti virtual company
Company Meeting · Product Review · $9/mo Pomodoro SaaS for developers
Background: A focus timer for devs that syncs with GitHub and Slack, sets a "focusing" status and mutes notifications during sessions.
Colleagues speak
ENTJ · Commander
Conditional go: the timer is a commodity, but "protect engineers' focus time across tools" is a real budget line for engineering managers. Reposition for teams and run a 2-week validation before writing more code.
INTJ · Strategic Architect
Conclusion first: a single-player timer at $9 loses to free apps in a race to zero. The defensible asset is the integration layer — Slack, GitHub, calendar — so design it as a focus-policy engine you can extend, not a countdown clock. [Assumption] devs will pay personally instead of expensing it.
ENTP · Debater
Flip the premise: do developers want a Pomodoro, or do they want fewer meetings? You may be treating the symptom. Try selling "meeting firewall" and see which landing page wins.
INTP · Logician
Define "focus session" before anything else — 25 fixed minutes contradicts how deep work actually behaves in code. Make the interval adaptive, or let a commit or PR event end the block.
ENFJ · Protagonist
The real buyer is the team lead who wants their people un-interrupted. Give them a gentle team view ("3 of 5 engineers in focus right now") without turning it into surveillance.
INFJ · Advocate
What people are really buying is permission to be unreachable without guilt. Your copy should sell that relief, not "productivity".
ENFP · Campaigner
The launch story writes itself: "I shipped my side project in 3 weeks after I started muting Slack." Seed 20 indie hackers and let them post their before/after.
INFP · Mediator
Be careful not to become another tool that makes devs feel watched. Keep personal stats private by default — that is a brand position, not just a setting.
ESTJ · Executive
Ship order: Slack status + DND first, GitHub second, team dashboard third. Each one gets a success metric before the next is built.
ISTJ · Logistician
Slack and GitHub OAuth scopes will get flagged by security teams, so request the minimum and document it. Plan SOC 2–lite answers now if you want team sales.
ESFJ · Consul
Ask 10 current users which tools they already pay for. If Clockwise or Reclaim are in the list, you need a crisp "why both" answer.
ISFJ · Defender
Don't break people's existing workflows: if your DND fails, someone misses an incident page. Add an "urgent passthrough" for on-call before launch.
ESTP · Entrepreneur
I could hack a Slack-only version this weekend. Put it in front of 3 dev Discords on Monday and count installs, not compliments.
ISTP · Virtuoso
Technically easy: Slack users.profile.set and DND APIs are straightforward. The hard part is reliability when tokens expire mid-session — build the retry logic first.
ESFP · Entertainer
The first 3 seconds should be one button: "Focus 50 min". Celebrate the end of a session with something fun, or nobody comes back on day two.
ISFP · Adventurer
Make it calm: a tiny menu-bar ring, soft colors, no streak shaming. Devs live in dark mode — design for it first.
Chair's synthesis · by ENTJ
- ✅ Consensus:
- A plain timer is a commodity; the integrations and "permission to be unreachable" are the value.
- $9 per individual is a hard sell; team pricing for engineering managers looks stronger.
- Privacy-by-default is non-negotiable.
- ⚠️ Key disagreements:
- INTJ (build an extensible focus-policy engine) vs ESTP (ship a Slack-only hack this weekend).
- ENTP (it's really a meeting problem) vs INTP (fix the focus model itself).
- 🎯 Open decisions:
- Individual tool or team product?
- "Pomodoro" positioning or "meeting firewall" positioning?
- 👉 Next steps:
- Run two landing pages (Focus Timer vs Meeting Firewall) for 7 days and compare waitlist signups.
- Ship a Slack-only MVP with on-call passthrough to 20 developers.
- Interview 5 engineering managers about paying $5–8 per seat.
Connects securely to your tools. The creator never sees your data.
About this skill
Individual decision-making often leads to blind spots in product strategy and technical architecture. This skill mitigates bias by simulating a virtual company meeting with 16 distinct MBTI personas to review your ideas. It forces a multi-perspective audit of features, business decisions, and risk factors in minutes.
What it does
- Multi-perspective auditing provides 16 unique viewpoints on a single proposal to identify hidden flaws.
- Structured persona simulation uses specific MBTI profiles to act as colleagues in roles like product, engineering, and management.
- Automated moderation ensures a structured flow where an ENTJ lead synthesizes consensus, disagreements, and next steps.
- Role-based debate generates focused 2-3 sentence critiques from each persona to prevent repetitive or vague feedback.
- Strategic synthesis distills the 16-way conversation into actionable items and unresolved questions.
How it works
- Define the scenario by providing a product idea, feature spec, or strategic decision for the team to review.
- Execute the meeting where 16 personas speak in a predefined order, providing concrete feedback based on their psychological profile.
- Review the synthesis generated by the ENTJ moderator to see where the team aligns and where the risks lie.
Frameworks & tools
This skill utilizes specialized Markdown orchestration files and persona definitions. It supports any text-based input including product requirement documents (PRDs), architectural diagrams, or business proposals.
Why this beats prompting it yourself
Generic "act as a team" prompts often result in repetitive, agreeable, or shallow feedback. This skill enforces strict constraints on persona length, prevents self-referential MBTI talk, and ensures at least 12 distinct viewpoints are expressed to maximize conflict and depth.
Use cases
- Product Reviews to find UX gaps or edge cases before development starts.
- Technical Architecture Debates to weigh trade-offs between speed, scalability, and maintainability.
- Business Strategy Stress-Testing to identify market risks or operational hurdles.
- Team Decision Support to simulate how different personality types will react to a change.
Known limitations
This skill is not for personality testing, code reviews, or casual chat. The persona files are in Chinese, though the meeting output will match the user's language.
Not for MBTI personality tests or code reviews. Internal persona files are in Chinese, though output is translated. Default product reviews use 2–3 sentences per persona.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 26 days ago
- Free with an Agensi account
Requires