[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YY1KAYVY6EC90N2C7YEED":3,"skill-same:01M72YY1KAYVY6EC90N2C7YEED":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M72YY1KAYVY6EC90N2C7YEED","competitive-war-room",null,"Run parallel competitor deep-dives and synthesize into positioning strategy and battle cards","enigmaicon-eng\u002FAI-Enterprise-OS","enigmaicon-eng","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269773191?v=4","01M72YXXYN7Q7BYRHV8RAVYNWD","01M72YXXZPW35H56D6F1XSK84D",2,"MIT","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fcompetitive-war-room\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: competitive-war-room\ndescription: \"Run parallel competitor deep-dives and synthesize into positioning strategy and battle cards\"\nuser-invocable: true\ndisable-model-invocation: true\nargument-hint: '\"\u003Ccompetitor1>, \u003Ccompetitor2>, \u003Ccompetitor3>\"'\nallowed-tools: Read, Glob, Grep, Task, WebSearch, WebFetch\n---\n\n# Competitive War Room\n\nRun parallel competitor deep-dives and synthesize into positioning strategy, battle cards, and competitive intelligence. One researcher per competitor, working simultaneously.\n\n## Usage\n\n```bash\n\u002Fagent-teams:competitive-war-room \"Notion, Coda, Slite\"\n```\n\n```bash\n\u002Fagent-teams:competitive-war-room \"Vercel, Netlify, Cloudflare Pages, Railway\"\n```\n\n---\n\n## Overview\n\nThis command spawns one market-researcher teammate per competitor. Each researcher does a deep-dive on their assigned competitor using WebSearch. The lead synthesizes individual deep-dives into:\n\n- Competitive positioning map\n- Differentiation opportunities\n- Competitive threats\n- Battle cards (one per competitor)\n- White space analysis\n\n**What you get:**\n\n- Deep-dive on each competitor (strategy, strengths, weaknesses, pricing, sentiment)\n- Side-by-side comparison across competitive dimensions\n- Battle cards ready for sales or product decisions\n- Specific strategic recommendations\n\n---\n\n## Competitors to Analyze\n\n$ARGUMENTS\n\n---\n\n## Instructions\n\n### Pre-Flight Check\n\n1. Verify Agent Teams is available in your Claude Code version.\n   If teammates cannot be spawned, display:\n\n   ```\n   This command requires Claude Code's Agent Teams feature.\n   Check https:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fdocs\u002Fclaude-code for setup instructions.\n   ```\n\n   If not available, stop.\n\n2. Parse the competitor list from the \"Competitors to Analyze\" section above.\n   - Trim whitespace from each competitor name\n   - Validate at least 2 competitors provided\n   - If fewer than 2: \"Please provide at least 2 competitors, separated by commas.\"\n\n3. Load product context for positioning baseline:\n   - Read `.claude\u002Fproduct-context\u002Fproduct-info.md` if it exists\n   - Read `.claude\u002Fproduct-context\u002Fcompetitive-landscape.md` if it exists\n   - If no product-info.md, ask the user: \"What's your product and who's it for? I need this to position you against competitors.\"\n\n---\n\n### Phase 1: Mission Briefing\n\n1. Define your product's positioning baseline from context files or user input.\n\n2. Display briefing:\n\n```\n── Competitive War Room ───────────────────────────────────\n\nYour Product: [product name and positioning from context]\n\nCompetitors to analyze:\n  [1. Competitor 1]\n  [2. Competitor 2]\n  [3. Competitor 3]\n  [... etc.]\n\nDeploying [N] market researchers (one per competitor).\nEach will deep-dive: strategy, strengths, weaknesses, pricing, sentiment.\n\nPhase 1: Parallel Deep-Dives ([N] researchers working simultaneously)\nPhase 2: Synthesis (positioning map, battle cards, recommendations)\n\nStarting research...\n───────────────────────────────────────────────────────────\n```\n\n---\n\n### Phase 2: Parallel Deep-Dives\n\nSpawn N market-researcher teammates simultaneously, one per competitor.\n\n**For each competitor, spawn a market-researcher with:**\n\n```\nPrompt: \"Deep-dive competitor: [Competitor Name].\n\nCONTEXT - YOUR PRODUCT:\n[Product info from context or user input]\n\nYour job: Become the expert on [Competitor Name]. Use WebSearch extensively\nto research:\n\n1. **Overview**: What they do, who they serve, how they position\n2. **Strategy**: Their approach to the market, recent moves, direction\n3. **Strengths**: What they do well (cite evidence from reviews, features)\n4. **Weaknesses**: Where they fall short (cite evidence from reviews, complaints)\n5. **Pricing**: Full pricing model with tiers (link to pricing page)\n6. **Customer Sentiment**: What users love and hate (G2, Capterra, Reddit, etc.)\n7. **Threat Level**: How much of a threat are they to [your product]?\n\nUse the standard market-researcher competitive war room output format.\nCite every claim with a source URL and date.\nBe thorough but focused. Quality over exhaustiveness.\"\n```\n\nWait for all researchers to complete their deep-dives.\n\n---\n\n### Phase 3: Synthesis\n\nAs the lead agent, compile all deep-dives into a competitive synthesis.\n\n1. Read all individual competitor deep-dives.\n\n2. Invoke the `team-deliverables` skill for the competitive synthesis template.\n\n3. Build the positioning map:\n   - Map your product against each competitor across key dimensions\n   - Identify where you're stronger, where you're weaker\n\n4. Identify differentiation opportunities:\n   - **Where you win**: Advantages to exploit\n   - **Where you lose**: Weaknesses to mitigate or avoid\n   - **White space**: Needs no competitor addresses well\n\n5. Assess competitive threats:\n   - Likelihood and impact of each threat\n   - Recommended response for each\n\n6. Generate battle cards:\n   - One per competitor using the battle card section of the template\n   - Include: their pitch, your counter, where you win, where they win, landmines, killer question\n\n7. Develop strategic recommendations:\n   - Positioning refinements based on competitive landscape\n   - Feature priorities informed by competitive gaps\n   - Messaging adjustments to highlight differentiation\n\n8. Present the completed competitive synthesis to the user.\n\n---\n\n### Phase 4: Cleanup\n\n1. Shut down all researcher teammates.\n\n2. Offer to save:\n\n```\nCompetitive war room complete.\n\nWould you like me to save these findings?\n\n  1. Full report → .claude\u002Fproduct-context\u002Fcompetitive-landscape.md\n  2. Battle cards → .claude\u002Fproduct-context\u002Fbattle-cards\u002F[competitor].md\n\nSaving makes this available to other PM agents (product-strategist,\nlaunch-planner, feature-prioritizer) for future reference.\n```\n\n3. If user accepts:\n   - Save competitive landscape to `.claude\u002Fproduct-context\u002Fcompetitive-landscape.md`\n   - Save individual battle cards to `.claude\u002Fproduct-context\u002Fbattle-cards\u002F` directory\n   - Include \"Last Updated: [date]\" header in each file\n\n4. If declined, done.\n\n---\n\n## Error Handling\n\n- If a researcher fails on a specific competitor, note the gap in the synthesis and proceed with available deep-dives.\n- If WebSearch is unavailable, note that data will be limited and work with available information.\n- If a competitor name is ambiguous (multiple companies with similar names), the researcher should clarify which one based on the product context.\n- If more than 5 competitors provided, warn the user that quality may decrease with too many parallel researchers, but proceed.\n\n## Related\n\n- `\u002Fagent-teams:validation-sprint` - Validate your idea against the competitive landscape\n- `\u002Fagent-teams:prd-stress-test` - Stress-test a PRD with competitive context\n","# Competitive War Room\n\nRun parallel competitor deep-dives and synthesize into positioning strategy, battle cards, and competitive intelligence. One researcher per competitor, working simultaneously.\n\n## Usage\n\n```bash\n\u002Fagent-teams:competitive-war-room \"Notion, Coda, Slite\"\n```\n\n```bash\n\u002Fagent-teams:competitive-war-room \"Vercel, Netlify, Cloudflare Pages, Railway\"\n```\n\n---\n\n## Overview\n\nThis command spawns one market-researcher teammate per competitor. Each researcher does a deep-dive on their assigned competitor using WebSearch. The lead synthesizes individual deep-dives into:\n\n- Competitive positioning map\n- Differentiation opportunities\n- Competitive threats\n- Battle cards (one per competitor)\n- White space analysis\n\n**What you get:**\n\n- Deep-dive on each competitor (strategy, strengths, weaknesses, pricing, sentiment)\n- Side-by-side comparison across competitive dimensions\n- Battle cards ready for sales or product decisions\n- Specific strategic recommendations\n\n---\n\n## Competitors to Analyze\n\n$ARGUMENTS\n\n---\n\n## Instructions\n\n### Pre-Flight Check\n\n1. Verify Agent Teams is available in your Claude Code version.\n   If teammates cannot be spawned, display:\n\n   ```\n   This command requires Claude Code's Agent Teams feature.\n   Check https:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fdocs\u002Fclaude-code for setup instructions.\n   ```\n\n   If not available, stop.\n\n2. Parse the competitor list from the \"Competitors to Analyze\" section above.\n   - Trim whitespace from each competitor name\n   - Validate at least 2 competitors provided\n   - If fewer than 2: \"Please provide at least 2 competitors, separated by commas.\"\n\n3. Load product context for positioning baseline:\n   - Read `.claude\u002Fproduct-context\u002Fproduct-info.md` if it exists\n   - Read `.claude\u002Fproduct-context\u002Fcompetitive-landscape.md` if it exists\n   - If no product-info.md, ask the user: \"What's your product and who's it for? I need this to position you against competitors.\"\n\n---\n\n### Phase 1: Mission Briefing\n\n1. Define your product's positioning baseline from context files or user input.\n\n2. Display briefing:\n\n```\n── Competitive War Room ───────────────────────────────────\n\nYour Product: [product name and positioning from context]\n\nCompetitors to analyze:\n  [1. Competitor 1]\n  [2. Competitor 2]\n  [3. Competitor 3]\n  [... etc.]\n\nDeploying [N] market researchers (one per competitor).\nEach will deep-dive: strategy, strengths, weaknesses, pricing, sentiment.\n\nPhase 1: Parallel Deep-Dives ([N] researchers working simultaneously)\nPhase 2: Synthesis (positioning map, battle cards, recommendations)\n\nStarting research...\n───────────────────────────────────────────────────────────\n```\n\n---\n\n### Phase 2: Parallel Deep-Dives\n\nSpawn N market-researcher teammates simultaneously, one per competitor.\n\n**For each competitor, spawn a market-researcher with:**\n\n```\nPrompt: \"Deep-dive competitor: [Competitor Name].\n\nCONTEXT - YOUR PRODUCT:\n[Product info from context or user input]\n\nYour job: Become the expert on [Competitor Name]. Use WebSearch extensively\nto research:\n\n1. **Overview**: What they do, who they serve, how they position\n2. **Strategy**: Their approach to the market, recent moves, direction\n3. **Strengths**: What they do well (cite evidence from reviews, features)\n4. **Weaknesses**: Where they fall short (cite evidence from reviews, complaints)\n5. **Pricing**: Full pricing model with tiers (link to pricing page)\n6. **Customer Sentiment**: What users love and hate (G2, Capterra, Reddit, etc.)\n7. **Threat Level**: How much of a threat are they to [your product]?\n\nUse the standard market-researcher competitive war room output format.\nCite every claim with a source URL and date.\nBe thorough but focused. Quality over exhaustiveness.\"\n```\n\nWait for all researchers to complete their deep-dives.\n\n---\n\n### Phase 3: Synthesis\n\nAs the lead agent, compile all deep-dives into a competitive synthesis.\n\n1. Read all individual competitor deep-dives.\n\n2. Invoke the `team-deliverables` skill for the competitive synthesis template.\n\n3. Build the positioning map:\n   - Map your product against each competitor across key dimensions\n   - Identify where you're stronger, where you're weaker\n\n4. Identify differentiation opportunities:\n   - **Where you win**: Advantages to exploit\n   - **Where you lose**: Weaknesses to mitigate or avoid\n   - **White space**: Needs no competitor addresses well\n\n5. Assess competitive threats:\n   - Likelihood and impact of each threat\n   - Recommended response for each\n\n6. Generate battle cards:\n   - One per competitor using the battle card section of the template\n   - Include: their pitch, your counter, where you win, where they win, landmines, killer question\n\n7. Develop strategic recommendations:\n   - Positioning refinements based on competitive landscape\n   - Feature priorities informed by competitive gaps\n   - Messaging adjustments to highlight differentiation\n\n8. Present the completed competitive synthesis to the user.\n\n---\n\n### Phase 4: Cleanup\n\n1. Shut down all researcher teammates.\n\n2. Offer to save:\n\n```\nCompetitive war room complete.\n\nWould you like me to save these findings?\n\n  1. Full report → .claude\u002Fproduct-context\u002Fcompetitive-landscape.md\n  2. Battle cards → .claude\u002Fproduct-context\u002Fbattle-cards\u002F[competitor].md\n\nSaving makes this available to other PM agents (product-strategist,\nlaunch-planner, feature-prioritizer) for future reference.\n```\n\n3. If user accepts:\n   - Save competitive landscape to `.claude\u002Fproduct-context\u002Fcompetitive-landscape.md`\n   - Save individual battle cards to `.claude\u002Fproduct-context\u002Fbattle-cards\u002F` directory\n   - Include \"Last Updated: [date]\" header in each file\n\n4. If declined, done.\n\n---\n\n## Error Handling\n\n- If a researcher fails on a specific competitor, note the gap in the synthesis and proceed with available deep-dives.\n- If WebSearch is unavailable, note that data will be limited and work with available information.\n- If a competitor name is ambiguous (multiple companies with similar names), the researcher should clarify which one based on the product context.\n- If more than 5 competitors provided, warn the user that quality may decrease with too many parallel researchers, but proceed.\n\n## Related\n\n- `\u002Fagent-teams:validation-sprint` - Validate your idea against the competitive landscape\n- `\u002Fagent-teams:prd-stress-test` - Stress-test a PRD with competitive context\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24,"user-invocable":25,"disable-model-invocation":25},"Read, Glob, Grep, Task, WebSearch, WebFetch","\"\u003Ccompetitor1>, \u003Ccompetitor2>, \u003Ccompetitor3>\"",true,"main","a4b48842f3e48549adf3dc335a8837c66da99497","agents\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fcompetitive-war-room",0,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng","2026-05-17 16:00:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill competitive-war-room",{"tool":39,"command":40},"bunx","bunx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill competitive-war-room",{"tool":42,"command":43},"pnpm","pnpm dlx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill competitive-war-room","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fcompetitive-war-room\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72ZGWW03JSE1T3TKK5NZ11Y","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72ZGT3FJT7QRM1VNQRKR0XD","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72ZGQ69DCF0SBP9JXFPWKJS","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72ZGNF126QT0MQ2D3DNGZRN","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72ZGHVJ9S0YXMNBHQGQ95BY","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72ZGFNZCHFY2FS3ZD9MCYV9","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]