cogni-trends

Assess 60 trend candidates from three stakeholder perspectives (foresight analyst, domain expert, pipeline consumer).

Recursive deep research on a single high-value trend candidate to enrich evidence before report writing.

Generate 60 scored trend candidates using multi-framework analysis (TIPS, Ansoff, Rogers, CRAAP). DO NOT USE DIRECTLY — invoked by trend-scout Phase 2.

Write a single investment theme (Handlungsfeld) section using the Corporate Visions arc (Why Change → Why Now → Why You → Why Pay) with investment thesis, strategic capabilities, and business case from enriched trend evidence. DO NOT USE DIRECTLY — invoked by trend-report Phase 2.

Evaluate a trend report against structural quality criteria across investment themes.

Revise a trend report after claims verification — apply corrections and find replacement evidence.

Generate a narrative TIPS dimension section with inline citations and verifiable claims from trend candidates. DO NOT USE DIRECTLY — invoked by trend-report Phase 1.

Evaluate and rank web research signals by quality, relevance, and diversity before candidate generation.

Execute bilingual web research (EN/DE) for trend scouting and return aggregated signals as compact JSON. DO NOT USE DIRECTLY — invoked by trend-scout Phase 1.

Generate a strategic TIPS trend report organized around investment themes (Handlungsfelder) with inline citations and verifiable claims. The user selects a report-level narrative arc from cogni-narrative's 7 story arcs (corporate-visions, technology-futures, competitive-intelligence, strategic-foresight, industry-transformation, trend-panorama, theme-thesis) — the arc frames the executive summary, bridge paragraphs between themes, and a synthesis closing section that bind investment themes into one cohesive narrative. Each investment theme internally uses the theme-thesis arc (Why Change → Why Now → Why You → Why Pay) backed by T→I→P→S value chain evidence. Reads agreed trend candidates, enriches each with web-sourced quantitative evidence via parallel agents, assembles the report with arc-framed executive summary, bridge paragraphs, theme sections, synthesis section, and claims registry. Invokes cogni-claims:claims for optional verification. Downstream polish, visualization, and export are steered via `/trends-resume`. Required pipeline: trend-scout → value-modeler → trend-report. Use when: (1) trend-scout and value-modeler have completed, (2) user wants a written trend report, (3) user mentions "trend report", "TIPS report", "write up trends", "summarize trends", "trend analysis document", "strategic stories", (4) preparing a deliverable from scouted trends, (5) user asks to "generate report from trends" or "create trend deliverable". Always use this skill when trend-scout output exists and the user wants any kind of written trend analysis — even if they don't use the exact phrase "trend report".

Interactive trend scouting workflow with industry selection, bilingual support (DE/EN), and downstream pipeline integration. Scouts trends across 4 dimensions (each trend gets full TIPS expansion). Creates research projects with 60 industry-contextualized trend candidates that feed directly into value-modeler or trend-report. Use when: (1) Starting smarter-service research with industry context, (2) User wants to scout trends for a specific industry and subsector, (3) User mentions "trend scouting", "industry trends", "trend scout", (4) Preparing input for the TIPS pipeline (value-modeler, trend-report).

Manage persistent industry catalogs that accumulate TIPS knowledge across pursuits. Use whenever the user mentions "industry catalog", "catalog", "initialize catalog", "import to catalog", "promote to catalog", "catalog status", "list catalogs", "create catalog", "export catalog", "catalog analytics", "cross-pursuit", "reusable patterns", "industry knowledge base", or wants to manage the persistent repository of TIPs, Solution Templates, SPIs, Metrics, and Collaterals that new pursuits inherit from. Also trigger when the user has completed value-modeler curation (Phase 5) and wants to actually persist the recommendations.

Generate an interactive HTML dashboard showing the full TIPS project lifecycle. Use whenever the user mentions tips dashboard, trend dashboard, TIPS overview, "show me the trends", "visualize tips", "tips project view", TIPS status dashboard, or wants to see all trend scouting data in a browser — even if they don't say "dashboard". Also trigger at the end of heavy TIPS sessions (after trend-report, value-modeler, or catalog import) as a capstone visualization.

Resume, continue, or check status of a TIPS trend scouting project. Use whenever the user mentions "continue tips", "resume tips", "resume trends", "where was I", "tips status", "what's next", "continue the project", "resume trend project", "check scan progress", "trend status", or opens a session that involves an existing cogni-trends project — even if they don't say "resume" explicitly.

Build TIPS relationship networks and generate ranked Solution Templates from agreed trend candidates. Use whenever the user mentions "value modeler", "solution mapping", "TIPS paths", "relationship networks", "solution templates", "big block", "solution diagram", "rank solutions", "business relevance scoring", "map trends to solutions", "what should we build", "which solutions matter", "prioritize solutions", "re-anchor solutions", "remap blueprints", "rebuild portfolio mapping", "re-anchor STs", or wants to go from trend insights to actionable, ranked solution recommendations. Also trigger when the user has completed a trend-scout project and asks "what's next" or "now what".