research

Research and plan scalable technical solutions with structured phases and citations.

5|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/namdfang/claudfang-engineer --skill research-namdfang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/namdfang/claudfang-engineer/tree/main/.claude/skills/research
Command: npx skills add https://github.com/namdfang/claudfang-engineer --skill research-namdfang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you clearly define research scope, gather information from multiple sources, evaluate sources, and synthesize a concise plan and report for scalable, secure, and maintainable technical solutions.

Core Features & Use Cases

  • Structured research phases: Scope definition, information gathering, analysis, and synthesis.
  • Tooling strategy: Phase guidance for using sources, citations, and evaluation criteria.
  • Report generation: Produces executive summaries and actionable recommendations.

Quick Start

Use the research skill to outline a definition of scope for a new microservice and prepare a high-level plan document.

Frequently Asked Questions about research

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

FAQPage Schema
How do I plan and document a scalable technical solution?

Planning a scalable technical solution requires structured research across scope definition, information gathering, source validation, and synthesis into a comprehensive roadmap. This skill guides you through phase-based methodology to produce actionable recommendations addressing functional and technical requirements.

What's the best way to gather and validate information from multiple sources for architecture decisions?

Multi-source information gathering involves defining research scope, collecting data from varied sources, evaluating credibility with citations, and cross-validating findings. This approach ensures your architecture and engineering decisions rest on vetted, traceable evidence rather than single sources.

How do I structure a research report with security and risk assessment for a new microservice?

A structured research report combines scope definition, gathered information, risk and security analysis, and synthesis into executive summaries with actionable recommendations. This produces traceable, maintainable deliverables suitable for engineering and product initiatives.

When should I use systematic research and documentation for technical initiatives?

Systematic research applies to engineering, architecture, and product initiatives requiring clear scope, multi-source validation, security considerations, and implementation roadmaps. Use it when decisions demand phase-based methodology, controlled tool usage, and comprehensive, auditable outputs.

Can I use research planning for both initial architecture definition and ongoing solution maintenance?

Yes. Structured research phases support both initial scope definition and ongoing evaluation of maintainability and security. The phase-based methodology and cross-source validation make it applicable to defining new solutions and assessing existing technical approaches.