deep-research

Coordinate multi-day technology research into stakeholder-ready reports with structured templates.

8|2|Updated Jan 15, 2026

Search Tags:#architecture #research #competitive-analysis #deep-research #evidence-evaluation #multi-day #stakeholder-report

Ready to run

npx skills add https://github.com/srstomp/pokayokay --skill deep-research-srstomp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deep-research
Source: https://github.com/srstomp/pokayokay/tree/main/plugins/pokayokay/skills/deep-research
Command: npx skills add https://github.com/srstomp/pokayokay --skill deep-research-srstomp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinated long-form technology research is complex and time-consuming, and this skill provides a structured approach to orchestrate multi-day investigations and deliver stakeholder-ready reports.

Core Features & Use Cases

Research planning and question framing to drive focused investigations
Evidence gathering, synthesis, and comparison using templates such as research reports and comparison matrices
Stakeholder-ready outputs with structured recommendations and decision rationale
Continuity across sessions (ohno-based workflows) to maintain context and traceability

Quick Start

Define research questions and gather sources to produce a stakeholder-ready report.

Frequently Asked Questions about deep-research

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

FAQPage Schema

How do I structure multi-day technical research into a stakeholder report?▼

To structure multi-day technical research into a stakeholder report, define research questions, gather sources, evaluate evidence, and synthesize findings using templates like research reports and comparison matrices.

What is the best way to conduct competitive analysis for engineering and product teams?▼

The best way to conduct competitive analysis is using a repeatable framework that coordinates evidence gathering and comparison matrices, delivering structured recommendations and decision rationale tailored for engineering and product teams.

How does evidence evaluation work during architecture exploration?▼

Evidence evaluation during architecture exploration works by systematically gathering sources, assessing their validity, and synthesizing the data into comparison matrices to drive focused investigations and platform evaluations.

Can I maintain context and continuity across multi-day research sessions?▼

Yes, you can maintain context and continuity across multi-day research sessions using ohno-based workflows, which preserve traceability and ensure coordinated long-form investigations remain aligned with the original research questions.

Does this structured research approach require specific platform dependencies?▼

No, this structured research approach does not require specific platform dependencies, allowing you to apply the framework to platform evaluations and decision papers across various product, engineering, and research environments.

When should I use a comparison matrix for technology research?▼

You should use a comparison matrix for technology research when you need to evaluate multiple platforms or architectures, synthesizing gathered evidence into a structured format to present clear decision rationale to stakeholders.