Skip to content

Need to add an agent called "Research" #2

Description

@rasool404

Overview

Currently, this repo provides profiles for development-focused workflows, but there is no dedicated agent optimized for researching and understanding external documentation before implementation.

When working on new integrations, SDKs, APIs, frameworks, or unfamiliar libraries, developers often need an agent that can:

  • Read and analyze API documentation
  • Compare different approaches from official docs
  • Extract implementation requirements
  • Summarize authentication flows
  • Identify SDK usage patterns
  • Research breaking changes and migration guides
  • Gather examples before code generation

A dedicated Research agent would improve development workflows by separating discovery and research tasks from implementation tasks.


Example Use Cases

1. API Integration Research

Prompt:

Research the Stripe API documentation and summarize:

  • Authentication requirements
  • Customer creation flow
  • Payment Intent workflow
  • Relevant rate limits
  • Recommended implementation approach

Expected Output:

  • High-level architecture overview
  • Authentication model explanation
  • Key API endpoints and workflows
  • Important limitations and considerations
  • Suggested implementation strategy
  • Links to relevant documentation sections

2. Framework Research

Prompt:

Research Next.js caching strategies and explain:

  • Server Components caching
  • Route cache behavior
  • Revalidation options
  • Recommended patterns

Expected Output:

  • Overview of caching layers
  • Cache invalidation mechanisms
  • Common implementation patterns
  • Tradeoffs between approaches
  • Best-practice recommendations
  • References to official documentation

Benefits

  • Separates research from implementation workflows
  • Reduces context switching for developers
  • Encourages documentation-first development
  • Produces more accurate implementation plans
  • Improves onboarding for unfamiliar technologies
  • Helps identify risks and limitations before coding

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions