research

Decompose research topics and evaluate sources with decision gates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill research-pyl-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/research
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill research-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted engineering by forcing thorough, evidence-backed discovery so implementations aren’t based on guesswork or outdated assumptions.

Core Features & Use Cases

  • DISCOVER-first workflow: Runs a structured research process before the spec so findings directly shape what gets built.
  • Deep documentation coverage: Reads full reference documentation for each sub-question instead of relying on overviews.
  • Deterministic evidence rules: Uses a clear decision matrix to Adopt, Adapt, or Build-New and avoids reinventing existing solutions.
  • External API rigor: Treats official API documentation as the primary source of truth and validates schemas by requiring contract artifacts and inline citations for verifiability.
  • Codemap-scoped search: Optionally loads project codemaps to constrain searches to the relevant modules and paths.

Quick Start

Use the research skill to produce a spec-ready evidence package by decomposing your topic, scoping searches with project codemaps, consulting official reference docs (and real API docs when applicable), and writing conflict-aware findings with citations.

Frequently Asked Questions about research

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

FAQPage Schema
How do I gather documentation and evidence before writing a project specification?

To gather evidence before writing a specification, decompose research topics into sub-questions, read full reference documentation, and evaluate sources using decision gates to produce citation-backed findings.

What is the best way to research external API integrations for a new feature?

The best way to research external API integrations is to treat official API documentation as the primary source of truth, validate schemas by requiring contract artifacts, and generate inline citations for verifiability.

How do I scope a codebase search when researching component planning topics?

Scope codebase searches for component planning by loading project codemaps to constrain queries to relevant modules and paths, ensuring the research output directly shapes what gets built.

When should I use a decision matrix to evaluate libraries for adoption?

Use a decision matrix to evaluate libraries during the discovery stage to determine whether to adopt, adapt, or build-new, avoiding wasted engineering on reinventing existing solutions.

Does the research workflow produce code or specification outputs?

The research workflow produces spec-ready evidence packages and citation-backed findings rather than code, ensuring implementations are based on verifiable documentation instead of guesswork.