shep-kit:research

Generate research.yaml and Markdown documentation for feature implementation decisions.

241|51|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/shep-ai/cli --skill shep-kit-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shep-kit:research
Source: https://github.com/shep-ai/cli/tree/main/.claude/skills/shep-kit%3Aresearch
Command: npx skills add https://github.com/shep-ai/cli --skill shep-kit-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured workflow to analyze technical approaches for a feature, compare libraries and architectures, and document rationale to support timely implementation planning.

Core Features & Use Cases

  • Gate-driven research ensures all open questions in the feature spec are resolved before proceeding.
  • Decisions & trade-offs identify technology/library choices, architecture patterns, and integration approaches with rationale.
  • Artifacts generation automatically writes research.yaml and generates Markdown documentation for developer planning.

Quick Start

Run research on the current feature by invoking /shep-kit:research after the feature spec is prepared.

Frequently Asked Questions about shep-kit:research

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

FAQPage Schema
How do I document technical decisions and evaluate library options for feature development?

To document technical decisions, the research workflow identifies library options and architecture patterns, records rationale, and generates a Markdown file alongside structured YAML. This ensures your feature development captures trade-offs and supports implementation planning.

What is the best way to resolve open questions in a feature spec before implementation?

Resolving open questions requires a gate-driven research workflow that reads your spec file, checks for unresolved items, and blocks implementation until all queries are answered. This ensures technical choices are fully evaluated before development proceeds.

How do I generate research documentation from a spec file for technology decisions?

Generating research documentation involves reading the spec for open questions, evaluating library and architecture options, and automatically writing a research YAML file with a Markdown document. This captures trade-offs and rationale for developer planning.

Can I compare multiple architecture patterns and integration approaches before starting feature work?

Yes, comparing multiple architecture patterns and integration approaches is the core function of this technical research workflow. It evaluates technology choices against your feature requirements and documents the specific trade-offs and rationale for each architectural option.

Do I need a prepared feature spec to analyze technical approaches and trade-offs?

Yes, a prepared feature spec is required to analyze technical approaches. The research workflow reads the spec file to identify open questions, making it a prerequisite for generating decision rationale and evaluating trade-offs.