metodologia-technology-vigilance

Synthesize multi-source technology signals into a vigilance report with source-tagged recommendations.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-technology-vigilance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metodologia-technology-vigilance
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/change/technology-vigilance
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-technology-vigilance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Technology Vigilance helps teams systematically detect, validate, and synthesize signals from analyst reports, academic research, open-source communities, and thought leaders to produce actionable technology intelligence.

Core Features & Use Cases

  • Multi-source signal collection and triangulation across tiers (analyst, academic, OSINT, and thought leaders)
  • Convergence/divergence analysis to resolve conflicting signals and identify opportunities
  • Adoption curve positioning using Rogers proxies and multi-source evidence
  • Sector relevance filtering and cross-sector mapping to tailor insights for specific industries
  • Deliverables in multiple formats with explicit source tagging and traceability

Quick Start

Run a full technology vigilance scan for your project and return structured, actionable insights.

Frequently Asked Questions about metodologia-technology-vigilance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is technology vigilance and how does multi-source signal triangulation work?

Technology vigilance systematically detects and validates signals across analyst, academic, open-source, and thought-leader sources. Multi-source triangulation cross-references these tiers to resolve conflicting data and synthesize actionable technology intelligence for product teams.

How do I build a technology radar using OSINT and adoption curve analysis?

Build a technology radar by collecting OSINT signals and mapping them against Rogers adoption curve proxies. This Skill positions technologies on the curve using multi-source evidence to produce a structured landscape surveillance report.

Can I filter technology vigilance reports for specific industry sectors?

Yes, sector relevance filtering and cross-sector mapping tailor insights for specific industries. This allows product teams to customize landscape surveillance outputs and focus on sector-specific signals relevant to their strategic initiatives.

What is the best way to analyze convergence and divergence in technology signals?

The best way to analyze convergence and divergence is multi-source triangulation across analyst and academic tiers. This approach identifies where multiple sources align or conflict, highlighting strategic opportunities and validating technology trends.

Does this technology vigilance methodology provide actionable recommendations with source tagging?

Yes, the methodology generates MUST, SHOULD, and COULD recommendations with explicit source tagging and traceability. This ensures all actionable insights derived from the vigilance scan are backed by verifiable analyst, academic, or OSINT evidence.