team

Simulates a four-role team discussion covering product, requirements, architecture, and QA perspectives.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/dan10002ht/shopify-template --skill team-dan10002ht
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/dan10002ht/shopify-template/tree/main/.claude/skills/team
Command: npx skills add https://github.com/dan10002ht/shopify-template --skill team-dan10002ht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Making product or architecture decisions alone often misses critical angles like business value, edge cases, technical feasibility, and testability. This Skill convenes a virtual team of four senior roles (PM, BA, Tech Lead, QA) to debate any topic and surface blind spots before you commit. ## Core Features & Use Cases - Multi-Perspective Review: Each topic is analyzed from Product, Business Analysis, Technical, and QA viewpoints in a structured format. - Honest Debate: Roles challenge each other (e.g., Tech Lead pushes back on oversized scope, QA flags missing test coverage) instead of fake consensus. - Actionable Output: Every session ends with agreements, trade-offs, action items with owners, and decisions needing your input. - Use Case: Before kicking off a new Shopify app feature, ask the team to review the plan and receive effort estimates (S/M/L/XL), risk areas, and a test strategy in one response. ## Quick Start Invoke the team skill with a topic such as "discuss the architecture for adding a background job queue to the app" to get a full four-role review.

Frequently Asked Questions about team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get multiple perspectives on a product decision from AI?

Invoke the team skill with your topic as the argument. It responds as four roles (PM, BA, Tech Lead, QA), each giving their professional assessment, followed by alignment points, trade-offs, and action items.

What roles does the team meeting skill simulate?

It simulates four senior roles: a CPO-level Product Manager, a Principal Business Analyst, a Principal Engineer (Tech Lead), and a Principal QA/SDET. Each contributes domain-specific analysis to the discussion.

Can I use this for architecture review before implementation?

Yes. The Tech Lead role assesses technical feasibility, architecture implications, and effort using T-shirt sizing (S/M/L/XL), while QA evaluates testability and risk areas, making it suitable for pre-implementation review.

Does the team skill always reach consensus?

No. The instructions explicitly forbid fake consensus. Roles must challenge each other when they see problems, and disagreements are presented with both sides so you can make the final decision.

What language does the team discussion output use?

The discussion is conducted in Vietnamese with technical terms kept in English, as specified in the skill instructions. The structured format (PM, BA, TL, QA sections) remains consistent regardless of topic.