From saas-strategy
Use this skill when the user wants to analyze a SaaS company's market position, competitive landscape, product opportunities, or AI readiness. Triggers on: "analyze [company]", "competitive analysis", "market positioning", "AI readiness assessment", "SaaS strategy", "product opportunities", "where should we focus", "how do we compare to competitors".
How this skill is triggered — by the user, by Claude, or both
Slash command
/saas-strategy:saas-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill delivers McKinsey/Deloitte-style strategic analysis of SaaS companies. It activates when a user requests competitive intelligence, market positioning assessment, product opportunity mapping, or AI readiness evaluation. The main entry point is the `/saas-analyze` command.
This skill delivers McKinsey/Deloitte-style strategic analysis of SaaS companies. It activates when a user requests competitive intelligence, market positioning assessment, product opportunity mapping, or AI readiness evaluation. The main entry point is the /saas-analyze command.
The skill runs a structured multi-agent workflow — beginning with an iterative Discovery Call to scope the engagement, followed by parallel research, synthesis, source verification, and final report generation.
The /saas-analyze command launches the full workflow. Users may invoke it with or without arguments:
/saas-analyze — starts the Discovery Call intake with no prior context/saas-analyze [company name] — pre-fills the subject; Discovery Call continues from Step A2/saas-analyze [company name] [strategic question] — pre-fills subject and question; Discovery Call continues from Step A3Six specialized agents execute the analysis. Each has a defined role and a bounded scope:
| Agent | Role | Phase |
|---|---|---|
| Discovery Facilitator | Conducts the structured intake interview, builds the Analysis Brief, confirms scope | A |
| Market Intelligence Analyst | Researches market size, trends, TAM/SAM/SOM, industry reports, technology adoption curves | B |
| Competitive Intelligence Analyst | Profiles competitors, maps features, pricing, positioning, job postings, and recent moves | B |
| Product & AI Analyst | Audits product capabilities, reviews GitHub/changelog, scores AI maturity, identifies gaps | B |
| Lead Strategist | Synthesizes all research streams into strategic insights, recommendations, and opportunity rankings | D |
| Source Verifier | Reviews all claims across the draft report, annotates confidence levels, flags anything below the 20% verified-data threshold | E |
| Report Architect | Assembles the final deliverables: five Markdown files plus a self-contained HTML report with inline SVG charts | F |
The Discovery Call (Phase A) is iterative — the Discovery Facilitator asks questions one group at a time, waits for user responses, and refines the scope before proceeding. It never fires all questions at once.
The five steps are:
analysis-brief.md, confirm what can be analyzed with high vs. low confidence given available dataOnly after Step 5 is confirmed does the workflow advance to Phase B.
Agents should consult the following references throughout execution:
references/strategic-frameworks.md — descriptions of all analytical frameworks used, when to apply them, and which agent owns eachreferences/analysis-phases.md — detailed phase-by-phase workflow including timing estimates, re-research triggers, and language propagation rulesreferences/output-formats.md — exact structure for all Markdown outputs, HTML report sections, and SVG chart specifications with coordinatesreferences/data-sources.md — ranked list of trusted public data sources by category, with guidance on what to extract and what confidence level to assignreferences/citation-protocol.md — citation format, four confidence levels (VERIFIED / ESTIMATED / INFERRED / UNVERIFIED), and the anti-hallucination checklist every agent must run before writing a number into a reportCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub mnohosten/claude-saas-strategy