research

Creates factual QRDSI research artifacts documenting system behavior, constraints, code paths, vocabulary, risks and unknowns.

1|1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/luan/agents --skill research-luan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/luan/agents/tree/main/skills/research
Command: npx skills add https://github.com/luan/agents --skill research-luan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents design and implementation from being driven by assumptions by creating a factual QRDSPI research artifact about how the system behaves today.

Core Features & Use Cases

  • Evidence-first system reality: Captures behavior, constraints, code paths, vocabulary, risks, and unknowns as verified facts rather than proposed solutions.
  • Vault-aware context preservation: Loads relevant existing artifacts and carries forward resolved user decisions, defaults, non-goals, and scope boundaries while avoiding relitigation.
  • Plannotator-gated artifact review: Runs an artifact gate for the absolute path to ensure the research artifact is accepted before any commit.
  • Use Case: When you need to refactor or plan a new feature, first produce a research artifact that documents what the system currently does, where it does it, and what remains uncertain.

Quick Start

Create or update a research artifact by asking: research “what is the current behavior and code path for <topic>?” --depth high --auto.

Frequently Asked Questions about research

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

FAQPage Schema
How do I document current system behavior and code paths before starting a refactor?

To document current system behavior before a refactor, you need an evidence-first research artifact that captures verified facts, constraints, and code paths rather than proposed solutions. This prevents design and implementation from being driven by assumptions.

What is the best way to gather verified evidence for system research?

The best way to gather verified evidence for system research is by exploring the codebase and vault to capture behavior, constraints, vocabulary, risks, and unknowns, ensuring the artifact accurately describes current system reality.

How do I preserve existing context and resolved decisions when drafting a research artifact?

To preserve existing context when drafting a research artifact, load relevant existing artifacts from the vault and carry forward resolved user decisions, defaults, non-goals, and scope boundaries to avoid relitigating previously settled topics.

Can I get an artifact review and approval before committing system research?

Yes, you can obtain artifact approval before committing by running a Plannotator gate for the absolute path, ensuring the research artifact describing the system reality is fully accepted before any commit occurs.

When do I need to produce a factual research artifact for pre-design phases?

You need to produce a factual research artifact for pre-design or pre-implementation phases when evidence is required before planning, structure, or implementation decisions can be safely made without relying on assumptions.