research

Execute a research spike to produce findings and a proposed build layout.

14|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Cogni-DAO/node-template --skill research-cogni-dao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/Cogni-DAO/node-template/tree/main/.openclaw/skills/research
Command: npx skills add https://github.com/Cogni-DAO/node-template --skill research-cogni-dao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of conducting technical research spikes, producing comprehensive findings and proposed implementation layouts without generating actual code.

Core Features & Use Cases

  • Structured Research: Follows a defined process for understanding questions, researching options, and documenting findings.
  • OSS First Evaluation: Prioritizes surveying existing open-source solutions.
  • Proposed Layout: Generates a directional plan for how findings could be integrated into the system (projects, specs, tasks).
  • Use Case: When a new feature requires investigating different architectural approaches or external libraries, this Skill can be used to produce a clear, actionable research document and a high-level build plan.

Quick Start

Use the research skill to investigate options for integrating a new payment gateway.

Frequently Asked Questions about research

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

FAQPage Schema
How do I conduct a technical research spike for a new feature?

A technical research spike investigates existing codebases, surveys open-source options, and evaluates trade-offs to produce a comprehensive research document without writing code. It outputs structured findings and a proposed system build layout.

What is the best way to document architectural trade-offs before writing code?

Documenting architectural trade-offs involves exploring your existing codebase, identifying constraints, and evaluating different open-source libraries. The output is a dedicated research document containing findings and a proposed layout for system integration.

Can I generate a proposed build layout without actually writing implementation code?

Yes, you can generate a proposed build layout without writing implementation code by running a research spike. It surveys open-source solutions and evaluates constraints to produce a directional plan for projects, specs, and tasks.

How do I survey OSS options for integrating a new payment gateway?

To survey OSS options for a payment gateway, execute a research spike that prioritizes finding existing open-source solutions. It evaluates the trade-offs of different approaches and outputs a research document with integration findings.

When should I use a research spike instead of directly building a feature?

Use a research spike when a new feature requires investigating different architectural approaches or external libraries. It produces a clear, actionable research document and a high-level build plan rather than generating actual code.

Does this research process output code or just documentation?

This research process outputs documentation, not code. It generates a comprehensive research document in your docs directory and a loosely proposed layout for system integration, ensuring you have findings before implementation.