What problem does it solve? Project teams lose sight of whether their roadmap is the right plan for the business: delivery data, code health, and market signals live in separate places, and no one reconciles the CEO view (market, monetization, moat) with the CTO view (architecture, tech debt, delivery risk) into one decision-grade briefing. ## Core Features & Use Cases - Dual-lens briefing: Combines a CEO lens (market, competition, monetization, moat, focus, business risk) and a CTO lens (architecture health, tech debt, build-vs-buy, scaling, security, key-person risk) into one structured board briefing with a KPI scorecard. - Grounded analysis: Pulls delivery state from the think-and-ship MCP server (roadmap_, signal_, ship_*), code facts from the ministr MCP server, and market/competitor data from serpapi, labeling unverifiable claims as opinion. - Reversible decision feedback: Writes re-prioritization proposals, backlog bets, and captured signals back into the roadmap as proposals only — never auto-reordering or implementing. - Use Case: At the end of a quarter, run a full board briefing to get a scorecard of delivery velocity and gate health, a competitor and pricing scan, a ranked tech-debt register, and a decision queue of open strategic forks with recommendations. ## Quick Start Ask the assistant to run the business-intel skill to produce a full CEO and CTO board briefing for the current project.
