tech-research-pipeline

Orchestrate an eight-skill technical research workflow from brainstorming to decision synthesis.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/tomwangowa/agent-skills --skill tech-research-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-research-pipeline
Source: https://github.com/tomwangowa/agent-skills/tree/main/tech-research-pipeline
Command: npx skills add https://github.com/tomwangowa/agent-skills --skill tech-research-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of making critical technical decisions by providing a structured, multi-phase research and validation process that mitigates bias and ensures thoroughness.

Core Features & Use Cases

  • End-to-End Orchestration: Chains 8 specialized research skills, from brainstorming to decision synthesis.
  • Phased Validation: Incorporates empirical testing (Micro-PoC), falsification search, and self-auditing to rigorously test assumptions.
  • Gate Checks: Includes explicit decision points (Gate A, Gate B) for user approval and risk assessment.
  • Use Case: Evaluating a new technology for a critical production system, planning a major architectural migration, or making a significant build-vs-buy decision.

Quick Start

Initiate a full technical research pipeline for the question "Should we migrate from nodriver to Playwright for remote browser automation?" with high stakes and full depth.

Frequently Asked Questions about tech-research-pipeline

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

FAQPage Schema
How do I evaluate new technology for a production system migration?

Evaluating a major architectural migration requires a multi-phase technical research workflow that sequentially chains brainstorming, feasibility assessment, assumption extraction, and empirical validation to ensure rigorous verification.

What is the best way to validate technical feasibility before a build-vs-buy decision?

Validating technical feasibility for a build-vs-buy decision involves extracting core assumptions, running a micro-proof-of-concept validation, and executing critical research for falsification to rigorously test the proposed technical choice.

How do you perform risk assessment for critical technical decisions?

Risk assessment for critical technical decisions is performed through a phased validation pipeline incorporating micro-proof-of-concept testing, narrative auditing, cross-validation, and explicit gate checks for user approval.

Can I use a multi-phase research pipeline for planning major architectural migrations?

Yes, a multi-phase research pipeline is designed for planning major architectural migrations. It orchestrates end-to-end technical evaluation from initial brainstorming through final decision synthesis with built-in self-auditing checks.

Does the technical research workflow include decision points for user approval?

Yes, the technical research workflow includes explicit gate checks, specifically Gate A and Gate B, designed for user approval and risk assessment before proceeding to the next validation phase.