plugins/business/skills/saas-business-plan/SKILL.md
Strategic knowledge base for SaaS business planning and GTM strategy (2025-2026). Market sizing, audience/persona frameworks, competitive analysis, pricing models, positioning (April Dunford, Blue Ocean, Crossing the Chasm), GTM motions (PLG/SLG/hybrid), advertising benchmarks, and KPI targets. Used by the business-planner agent.
npx skillsauth add acaprino/anvil-toolset saas-business-planInstall 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.
Strategic reference material for building a SaaS business plan and go-to-market strategy. Updated for 2025-2026 market conditions.
| File | Phase | Content |
|------|-------|---------|
| references/market-sizing.md | Phase 1 | TAM/SAM/SOM calculation (3 methods), market saturation indicators, research tools |
| references/audience-personas.md | Phase 2 | ICP, buyer persona (P1/P2/P3), JTBD framework, customer research methods, early adopter channels |
| references/competitive-analysis.md | Phase 3 | Porter's 5 Forces in SaaS, positioning maps, Love/Hate/Want review analysis, CI tools |
| references/positioning-pmf.md | Phase 4 | April Dunford 5 steps, UVP, Crossing the Chasm, Blue Ocean ERRC, Sean Ellis PMF test |
| references/pricing.md | Phase 5 | Tiered/usage/hybrid/credit models, value-based pricing, Van Westendorp, pricing page best practices |
| references/go-to-market.md | Phase 6 | PLG vs SLG vs hybrid, channel-market fit by ACV, community-led growth, launch sequence |
| references/advertising-metrics.md | Phase 7 | Ad channel benchmarks, SEO/content ROI, email marketing, KPI benchmarks, North Star Metric |
| references/tools-resources.md | All | Tools by phase, templates, communities, books, 7-week timeline, final deliverable structure |
development
Quality gates for multi-reviewer code review pipelines: adversarial verification panel, completeness critic, reviewer pipeline conventions, and the context sharing pattern for parallel reviewers. TRIGGER WHEN: running /senior-review:team-review quality gates; running /senior-review:code-review Steps 4b/4c (adversarial verification and completeness check); consolidating or deduplicating findings from multiple parallel reviewers. DO NOT TRIGGER WHEN: single-reviewer style review without a consolidation phase, or generic team coordination (the upstream agent-teams skills cover that).
development
Knowledge base for pure-architecture decisions on when to unify duplicated logic into a shared abstraction versus leave it duplicated. Covers the canonical theory (Rule of Three, DRY/WET/AHA, Wrong Abstraction, Locality of Behaviour, Bounded Contexts, Tidy First options framing, CUPID vs SOLID), 12 essential-duplication patterns that justify unification, 12 wrong-abstraction patterns that justify inlining or decomposition, an operational decision frame, and a verified reading list. TRIGGER WHEN: the user is making an architectural decision about whether to centralize, extract, or remove a layer; reviewing an abstraction for premature generality; auditing scattered cross-cutting concerns; spawned by the abstraction-architect agent during /abstraction-architect:audit or as the Abstraction dimension of /senior-review:team-review or /senior-review:code-review; the user asks "should I extract this into a service" / "is this DRY enough" / "is this wrong abstraction". DO NOT TRIGGER WHEN: the task is code formatting and readability cleanup (use clean-code:clean-code), Python-specific refactoring with metrics (use python-development:python-refactor), generic dead-code removal (use senior-review:cleanup-dead-code), security review (use senior-review:security-auditor), or pure pattern-consistency review without an architecture lens (use senior-review:code-auditor).
development
Unified web frontend knowledge base covering CSS architecture, UX psychology, UI components, distinctive aesthetics, and interface design generation. TRIGGER WHEN: working on web styling, design systems, component decisions, responsive strategy, distinctive frontend aesthetics, or exploring multiple interface designs. DO NOT TRIGGER WHEN: the task is purely backend or unrelated to web frontend.
development
Stripe payments knowledge base - API patterns, checkout optimization, subscription lifecycle, pricing strategies, webhook reliability, Firebase integration, cost analysis, and revenue modeling. Loaded by stripe-integrator and revenue-optimizer agents; also consumable directly when the user asks for Stripe-specific patterns without needing an agent. TRIGGER WHEN: working with Stripe API (Payment Intents, Customers, Subscriptions, Checkout Sessions, Connect, webhooks, tax, usage-based billing), pricing strategy, or revenue modeling. DO NOT TRIGGER WHEN: payment work is non-Stripe (PayPal, Square, crypto) or the task is generic e-commerce unrelated to payments.