sdd-research

Analyze codebase patterns and external references to produce a research brief.

192|21|Updated Sep 19, 2025
One-click install
npx skills add https://github.com/madebyaris/spec-kit-command-cursor --skill sdd-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-research
Source: https://github.com/madebyaris/spec-kit-command-cursor/tree/main/.cursor/skills/sdd-research
Command: npx skills add https://github.com/madebyaris/spec-kit-command-cursor --skill sdd-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pattern investigation and technical research before specification. Use when technical approach is unclear, exploring existing solutions, or analyzing codebase patterns.

Core Features & Use Cases

  • Codebase Analysis: Identify existing patterns, conventions, and potential reuse opportunities.
  • External Solutions: Evaluate libraries or frameworks suitable for the problem.
  • Synthesis: Produce a concise research brief that informs the /specify and /plan steps.
  • Use Case: Before starting a new feature, run this skill to surface risks and core approaches.

Quick Start

Run the sdd-research skill on the current project to analyze patterns and gather references; review the generated research document and feed insights into the planning commands.

Frequently Asked Questions about sdd-research

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

FAQPage Schema
How do I analyze codebase patterns before starting a new feature?

Codebase pattern analysis identifies existing conventions and reuse opportunities by investigating your project structure. It surfaces risks and evaluates external libraries, producing a structured research document that informs your architecture decisions and guides subsequent specification steps.

When do I need technical research before writing a specification?

Technical research before specification is needed when the technical approach is unclear or you are evaluating external solutions. It performs pattern investigation and collects external references to produce a research brief that guides architecture decisions and risk assessment.

What's the best way to evaluate libraries and frameworks for an existing codebase?

Evaluating libraries for an existing codebase is done by running a pattern investigation that analyzes current conventions and collects external references. This produces a structured research document comparing external solutions against your project's specific reuse opportunities and risks.

Does this codebase analysis work without adding new dependencies to my project?

Yes, codebase analysis works without adding new project dependencies. It investigates existing patterns and evaluates external solutions conceptually, outputting a research document to guide specification and planning without modifying your current environment.

How do I assess technical risks during early project planning?

Assess technical risks during early planning by performing pattern investigation and technical research on the codebase. This analyzes existing conventions and external solutions, outputting a structured document that informs your risk analysis and architecture decisions.