mspec-research

Automate the mspec research phase and generate a research.md document.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/tubone24/mspec --skill mspec-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mspec-research
Source: https://github.com/tubone24/mspec/tree/main/.claude/skills/mspec-research
Command: npx skills add https://github.com/tubone24/mspec --skill mspec-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the research phase of the mspec workflow, helping users efficiently investigate through subagents and document findings.

Core Features & Use Cases

  • Subagent Integration: Utilizes the mspec-researcher subagent for detailed research.
  • Artifact Generation: Automatically produces a research.md document.
  • User Interaction: Facilitates user decisions on Open Choices directly within the Skill.
  • Workflow Validation: Ensures consistency and completeness of the research phase.

Quick Start

To initiate the research phase, run /mspec:research to investigate a change.

Frequently Asked Questions about mspec-research

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

FAQPage Schema
How do I automate the research phase for specification-driven development?

Automating the research phase for specification-driven development is handled by integrating with subagents to gather information and generating a structured research document. This streamlines investigations by documenting findings automatically.

What is the best way to document research findings for an mspec workflow?

The best way to document research findings for an mspec workflow is to automatically generate a research.md document. This ensures consistency and completeness while capturing detailed information gathered during the investigation.

Can I use subagents to investigate technical decisions for a software specification?

Yes, you can use subagents to investigate technical decisions for a software specification. The process utilizes a dedicated researcher subagent to perform detailed information gathering and facilitate user decisions on open choices.

How do I resolve open choices during a spec-driven development workflow?

Resolving open choices during a spec-driven development workflow is facilitated by direct user interaction within the research process. The system prompts for user input to make critical decisions and validate workflow consistency.

Do I need user input to complete the research phase of a specification workflow?

Yes, user input is required to complete the research phase of a specification workflow. The automated research process requires user interaction specifically to make decisions regarding open choices and ensure accurate decision support.