external-research

Aggregate Jira, Confluence, and GitHub research into a findings document.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/sergseven/agent-dev --skill external-research-sergseven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-research
Source: https://github.com/sergseven/agent-dev/tree/main/suites/reverse-spec/skills/external-research
Command: npx skills add https://github.com/sergseven/agent-dev --skill external-research-sergseven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill gathers intention, history, and dependency context for a codebase from external knowledge sources and produces a single findings document consumed by downstream workflows.

Core Features & Use Cases

  • Jira research (via Atlassian MCP) to surface epics and stories relevant to target domains.
  • Confluence research (via space searches) to capture pages and links to Jira issues for context.
  • GitHub dependency research to identify external references and usage patterns in the target repository.
  • Output: a consolidated findings document at spec/.external-research-findings.md for reverse-spec and spec-verify workflows.

Quick Start

Run the external-research skill against the target repository to generate spec/.external-research-findings.md

Frequently Asked Questions about external-research

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

FAQPage Schema
How do I consolidate external research from Jira, Confluence, and GitHub for a codebase?

To consolidate external research for a codebase, this skill aggregates epics and stories from Jira, domain content from Confluence, and dependency references from GitHub into a single findings markdown document.

How do I gather project context and history from Confluence and Jira for reverse-spec workflows?

Gather project context and history by running this skill to search Confluence spaces for domain pages and querying Jira for relevant issues, outputting a consolidated findings document for downstream reverse-spec workflows.

Can I scan GitHub repositories for external dependency usage patterns alongside Jira research?

Yes, you can scan GitHub repositories for external dependency usage patterns alongside Jira research by providing a project key and running the workflow to collate both results into a unified findings file.

What's the best way to generate a unified findings document from multiple external knowledge sources?

The best way to generate a unified findings document from multiple external knowledge sources is to run this aggregation workflow, which collates Jira, Confluence, and GitHub research into one markdown file.

Do I need an Atlassian project key to run external research on a codebase?

You need an Atlassian project key to trigger Jira research within the external research workflow, but Confluence searches and GitHub dependency scanning will still run and collate findings without one.

Where does the external research workflow write its consolidated findings output?

The external research workflow writes its consolidated findings output to spec/.external-research-findings.md, making the aggregated Jira, Confluence, and GitHub context available for spec-verify workflows.