research-solutions

Name: research-solutions
Availability: InStock
Author: marcus-friction

Search docs/solutions for prior solutions and extract root cause and steps.

3|Updated Feb 9, 2026

Search Tags:#planning #debugging #documentation #search #docs #solutions #knowledge-reuse

Ready to run

npx skills add https://github.com/marcus-friction/agents --skill research-solutions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: research-solutions
Source: https://github.com/marcus-friction/agents/tree/main/.agent/skills/research-solutions
Command: npx skills add https://github.com/marcus-friction/agents --skill research-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly locate relevant, previously documented solutions before planning or debugging to reduce duplication of effort and rework.

Core Features & Use Cases

Knowledge retrieval: locate past work from docs/solutions and summarize relevance.
Context extraction: pull root cause, solution steps, and prevention notes from prior docs.
Efficient planning: accelerate planning and debugging by reusing proven approaches.

Quick Start

Search the docs/solutions directory for past solutions relevant to your issue and review the most relevant results.

Frequently Asked Questions about research-solutions

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

FAQPage Schema

How do I find previously documented solutions before debugging or planning?▼

To find previously documented solutions before debugging or planning, search the docs/solutions directory to locate relevant past work, extract root causes and steps, and report findings for reuse.

What is knowledge reuse in software architecture reviews?▼

Knowledge reuse in software architecture reviews is the process of searching prior docs and solutions to extract root causes and prevention notes, accelerating planning by leveraging proven approaches.

How do I extract root cause and solution steps from existing documentation?▼

You extract root cause and solution steps from existing documentation by searching docs/solutions to locate relevant past work, pulling context such as root causes and prevention notes, and summarizing relevance.

Can I use this approach for both debugging and architecture reviews?▼

Yes, you can use this approach for both debugging and architecture reviews, as it locates relevant prior docs and solutions to save time and reduce duplication of effort across planning tasks.

What's the best way to prevent duplicate work when fixing recurring bugs?▼

The best way to prevent duplicate work when fixing recurring bugs is to search docs/solutions for past solutions, extract context such as root causes and steps, and apply those proven approaches.

Do I need a specific directory structure to search for past solutions?▼

Yes, you need a docs/solutions directory containing previously documented solutions to search, extract context such as root causes and steps, and report findings for implementation.