product-management/skills/competitive-brief/SKILL.md
Create a competitive analysis brief for one or more competitors or a feature area
npx skillsauth add grailautomation/claude-plugins competitive-briefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Create a competitive analysis brief for one or more competitors or a feature area.
/product-management:competitive-brief $ARGUMENTS
Ask the user:
Via web search:
If ~~knowledge base is connected:
If ~~chat is connected:
For each competitor:
Compare capabilities across key areas relevant to the analysis. See the competitive-analysis skill for rating frameworks and comparison matrix templates.
Analyze how each competitor positions themselves — target customer, category claim, key differentiator, and value proposition. See the competitive-analysis skill for positioning analysis frameworks.
For each competitor:
Based on the analysis:
Tie the analysis back to product strategy:
After generating the brief:
Use tables for feature comparisons. Use clear headers for each section. Keep the strategic implications section concise and actionable — this is where the value is for the reader.
development
Parse and analyze Workato recipe JSON exports. Use when the user asks about a Workato recipe's logic, data flow, field mappings, error handling, or control flow. Also use when the user references a .recipe.json file or asks to debug a Workato integration.
databases
Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.
tools
Use when the user invokes $spec-kit:tasks or /spec-kit:tasks, or asks to generate dependency-ordered tasks from the plan and repo context.
testing
Use when the user invokes $spec-kit:specify or /spec-kit:specify, or asks to create a brownfield-aware feature specification from a natural language description.