_research

Orchestrate dual-stanced research and generate directional guidance under research/.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/HahyeonJeon/gobbi --skill research-hahyeonjeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _research
Source: https://github.com/HahyeonJeon/gobbi/tree/main/plugins/gobbi/skills/_research
Command: npx skills add https://github.com/HahyeonJeon/gobbi --skill research-hahyeonjeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured guidance for post-plan execution by orchestrating dual researchers and producing reference-rich outputs that drive implementation decisions.

Core Features & Use Cases

  • Dual-stanced research (Innovative and Best-Practice) for each plan task to surface multiple perspectives and trade-offs.
  • Orchestrator synthesis that resolves conflicts and generates a single directional guidance per task.
  • Outputs stored under research/, including innovative.md, best.md, research.md, and results/, ensuring traceability and reuse.

Quick Start

Trigger the Step 3 research process to spawn dual researchers and generate the research/innovative.md, research/best.md, research/research.md, and research/results/ artifacts for the approved plan.

Frequently Asked Questions about _research

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

FAQPage Schema
What is dual-stanced research for software architecture planning?

Dual-stanced research evaluates design choices by generating both innovative and best-practice perspectives. It resolves conflicts through orchestration to produce single directional guidance, ensuring multiple viewpoints are considered before implementation begins.

How do I guide post-plan execution with codebase references?

You can guide execution by triggering a research process that analyzes unfamiliar code areas and design choices. It generates reference-rich markdown artifacts stored under the research directory, providing directional guidance without step-by-step implementation instructions.

When do I need structured research orchestration during software planning?

Structured research orchestration is needed during Step 3 of a plan task when design choices or unfamiliar code areas require directional guidance. It helps surface trade-offs and resolves conflicting perspectives before driving implementation decisions.

Can I use dual-stanced research to document architecture decisions for my codebase?

Yes, dual-stanced research produces traceable documentation by storing outputs in structured markdown files like innovative.md, best.md, and research.md. These artifacts capture multiple perspectives and synthesized guidance for future reference and reuse.

What's the best way to resolve conflicts between innovative and best-practice architectural approaches?

The best way is using an orchestrator synthesis that evaluates both innovative and best-practice stances. It resolves conflicts and generates a single directional guidance per task, ensuring implementation decisions are balanced and well-grounded.

Does this research process provide step-by-step implementation instructions for my plan tasks?

No, this research process intentionally avoids providing step-by-step implementation instructions. Instead, it produces directional guidance and codebase references that inform and guide the actual execution phase of your approved plan.