research-skill

Structure unresolved Delano delivery questions into project-scoped research intake and evidence capture.

7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/MajesteitBart/delano --skill research-skill-majesteitbart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-skill
Source: https://github.com/MajesteitBart/delano/tree/main/.agents/skills/research-skill
Command: npx skills add https://github.com/MajesteitBart/delano --skill research-skill-majesteitbart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps when a Delano request is not ready for direct changes because the scope, constraints, evidence, or tradeoffs still need investigation. It creates a disciplined research intake so planning does not drift into guesswork.

Core Features & Use Cases

  • Research intake setup: Opens a project-scoped research folder with task plan, findings, and progress files.
  • Evidence-led investigation: Guides inspection of local files, commands, and other sources before mutating canonical delivery artifacts.
  • Fold-forward workflow: Converts durable conclusions into spec, plan, decisions, workstreams, tasks, or updates when the evidence supports it.
  • Use case: Use this Skill when a delivery request has competing options, unclear intent, or missing evidence and you need to resolve the uncertainty first.

Quick Start

Use the research-skill to investigate this Delano request, identify the evidence I need, and draft a concise research intake before changing any canonical project files.

Frequently Asked Questions about research-skill

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

FAQPage Schema
How do I structure research intake for a project request with unclear scope?

Investigation validation requires inspecting local files, commands, and other sources to gather evidence before making changes, ensuring that competing options and missing evidence are resolved prior to canonical delivery artifact mutations.

When do I need to conduct evidence-led investigation before updating project artifacts?

Evidence-led investigation is needed when a delivery request has competing options, unclear intent, or missing evidence, requiring you to resolve uncertainty by inspecting local files and sources before changing canonical artifacts.

How do I fold forward research conclusions into a project plan or spec?

To fold forward research conclusions, convert durable findings into spec, plan, decisions, workstreams, tasks, or updates when the collected evidence supports justifying those canonical project changes.

What is the best way to handle a request with competing options and missing evidence?

The best way to handle competing options and missing evidence is to create a disciplined research intake that tracks project-scoped findings and progress, preventing planning from drifting into guesswork.

Does this research workflow require any specific dependencies or environment setup?

This research workflow operates without external dependencies, using native repository references to structure unresolved delivery questions into grounded evidence capture and project-scoped findings.