test-scenario

Structured framework for planning product launches, feature announcements, and go-to-market strategies. Organizes launches across five phases (internal, alpha, beta, early access, full) with specific actions and goals for each stage Uses the ORB framework to balance owned channels (email, blog, community), rented channels (social, app stores), and borrowed channels (guest posts, influencers, partnerships) Includes dedicated Product Hunt strategy with pre-launch preparation, launch-day tactics, and post-launch conversion guidance Provides launch checklist covering pre-launch setup, launch-day coordination, and post-launch user education and retention Emphasizes treating launches as ongoing moments rather than one-time events, with guidance on spacing feature announcements and maintaining momentum

SEO-optimized competitor comparison and alternative pages that position your product against rivals. Covers four page formats: singular alternatives, plural alternatives, you vs. competitor, and competitor vs. competitor comparisons Includes centralized competitor data architecture for consistent, maintainable information across all comparison pages Provides structured research process covering product features, pricing, reviews, and customer feedback with quarterly update cadence Emphasizes honest positioning that acknowledges competitor strengths and clearly defines who each product serves best

Web search with optional full-page content extraction from results. Returns real search results as JSON with optional --scrape flag to fetch complete page markdown for each result, avoiding redundant fetches Supports filtering by source type (web, images, news), category (GitHub, research, PDF), time range (past hour/day/week/month/year), location, and country Use --limit to control result count and --scrape-formats to customize output formats when extracting full content Part of a workflow escalation pattern: search first to discover URLs, then use dedicated scrape/map/crawl skills for deeper extraction

Bulk extract content from entire websites or site sections with depth and path filtering. Crawls pages following links up to configurable depth limits and page counts, with path inclusion/exclusion filters to scope extraction Supports async job polling or synchronous waiting with progress display via --wait and --progress flags Offers concurrency control, request delays, and JSON output formatting for integration into agent workflows Part of a four-step escalation pattern: search → scrape → map → crawl, used when single-page extraction is insufficient