Built comprehensive trend discovery and analysis system featuring:
- Trend Analyst agent with Internet Pipes expertise
- 6 specialized tasks: discover-trends, analyze-single-trend, generate-trend-report, compare-trends, forecast-trend, explore-niches
- 3 YAML templates for structured trend reporting
- 4 data resources: Internet Pipes framework, data sources catalog, validation checklist, trend categories
- Example demo report analyzing glowing sunscreen, butterfly pea tea, air quality monitors, and permanent jewelry
- Web bundles for IDE and web UI deployment
The Internet Pipes methodology enables discovering emerging trends by analyzing billions of digital footprints (searches, social media, purchases) across the web - revealing what people actually want before competitors do.
Features:
- Multi-source validation (search, social, commerce)
- Fad vs. trend assessment
- Opportunity scoring and niche discovery
- Strategic recommendations for entrepreneurs, creators, and investors
- Comprehensive validation checklists
Example use cases:
- Discover product opportunities before mainstream
- Identify underserved market segments
- Generate data-backed content strategies
- Validate business ideas with real-time signals
- Time market entry for optimal positioning
🤖 Generated with Claude Code (https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: add OpenCode integration implementation plan for BMAD-METHOD
* installer(opencode): add OpenCode target metadata in install.config.yaml
* chore(deps): add comment-json for JSONC parsing in OpenCode integration
* feat(installer/opencode): implement setupOpenCode with minimal instructions merge and BMAD-managed agents/commands
* feat(installer): add OpenCode (SST) to IDE selector and CLI --ide help
* fix(opencode): align generated opencode.json(c) with schema (instructions as strings; agent.prompt; command.template; remove unsupported fields)
* feat(installer): enhance OpenCode setup with agent selection and prefix options
* fix: update configuration file references from `bmad-core/core-config.yaml` to `.bmad-core/core-config.yaml` across multiple agent and task files for consistency and clarity.
* refactor: streamline OpenCode configuration prompts and normalize instruction paths for agents and tasks
* feat: add tools property to agent definitions for enhanced functionality. Otherwise opencode consders the subagents as readonly
* feat: add extraction of 'whenToUse' from agents markdown files for improved agent configuration in opencode
* feat: enhance task purpose extraction from markdown files with improved parsing and cleanup logic
* feat: add collision warnings for non-BMAD-managed agent and command keys during setup
* feat: generate and update AGENTS.md for OpenCode integration with agent and task details
* feat: add compact AGENTS.md generator and JSON-only integration for OpenCode
* chore(docs): remove completed OpenCode integration implementation plans
* feat: enable default prefixes for agent and command keys to avoid collisions
* fix: remove unnecessary line breaks in 'whenToUse' descriptions for QA agents to mathc the rest of the agents definitions and improve programatic parsing of whenToUse prop
* fix: update OpenCode references to remove 'SST' for consistency across documentation and configuration
* fix: update agent mode from 'subagent' to 'all' for consistency in agent definitions
* fix: consolidate 'whenToUse' description format for clarity and consistent parsing
* Godot Game Dev expansion pack for BMAD
* Workflow changes
* Workflow changes
* Fixing config.yaml, editing README.md to indicate correct workflow
* Fixing references to config.yaml, adding missing QA review to game-dev agent
* More game story creation fixes
* More game story creation fixes
* Adding built web agent file
* - Adding ability for QA agent to have preloaded context files similar to Dev agent.
- Fixing stray Unity references in game-architecture-tmpl.yaml
---------
Co-authored-by: Brian <bmadcode@gmail.com>
Claude
Javier Gomez
sjennings