shipit-kit:research

Analyze a feature's technical approach and document decisions in research.yaml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured evaluation of a feature's technical approach and documents decisions to inform implementation.

Core Features & Use Cases

  • Guided research workflow: identifies current feature context, analyzes technology decisions (libraries, architecture, integration approaches) and documents rationale to guide execution.
  • Produce actionable documentation: outputs a structured research.yaml with decisions, rationale, security and performance notes, and updates to related spec metadata.
  • Integrates with ShipIT SDLC: aligns with the /shipit-kit:new-feature workflow to enable planning and implementation routing.

Quick Start

Start a research session for the current feature branch by triggering the shipit-kit:research invocation.

Frequently Asked Questions about shipit-kit:research

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

FAQPage Schema
How do I document technical architecture decisions for a new feature?

To document technical architecture decisions, this Skill analyzes your feature's technical approach, evaluates library choices and trade-offs, and outputs a structured research.yaml file containing rationale, security notes, and performance considerations.

What is the best way to evaluate libraries and architecture trade-offs before implementation?

Evaluating library and architecture trade-offs is handled by applying a guided research workflow to your feature spec, producing structured decision documentation with security and performance notes to guide future implementation planning.

How do I generate a research.yaml file for feature planning?

Generating a research.yaml file requires starting a research session on your current feature branch, which analyzes integration approaches and architecture choices to update related spec metadata with actionable decision rationale.

Can I use this technical analysis workflow for features on my current git branch?

Yes, you can apply this technical analysis workflow directly to features on your current branch or a specified spec, automatically identifying context and evaluating technology decisions to inform implementation.

Does this feature research workflow integrate with existing SDLC processes?

Integrating with SDLC processes is supported natively, as the workflow aligns with the ShipIT new-feature workflow to enable seamless planning and implementation routing based on the documented technical decisions.

What should I include in feature planning documentation for future reference?

Feature planning documentation should include technical decisions, rationale, security notes, and performance evaluations, which this Skill automatically structures into a research.yaml file alongside updates to related feature YAML metadata.