flywheel-research

Researches external GitHub repositories through a multi-agent pipeline to extract implementation insights.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-research-burningportra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flywheel-research
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/flywheel-research
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-research-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Studying an unfamiliar open-source codebase by hand is slow and shallow: you skim the README, miss the architecture, and never surface the anti-patterns worth avoiding. This Skill runs a structured multi-agent research pipeline that investigates, deepens, inverts, and synthesizes findings from any external Git repository. ## Core Features & Use Cases - 7-Phase Research Pipeline: Clones a repository (with HTTPS-only host allowlisting and HEAD SHA pinning), then runs parallel Explore and general-purpose agents to map architecture, deepen key areas, invert assumptions, and hunt for blunders. - Multi-Model Synthesis: Spawns parallel Opus and Sonnet Plan agents that write application-focused and ergonomics-focused findings to docs/research/, then merges everything into a sourced research proposal. - Major Feature Integration Mode: Extends research with an integration proposal, iterative deepening, five blunder-hunt passes, and cross-model feedback when the goal is adopting a feature rather than just learning. - Use Case: Point it at a repo like a terminal multiplexer or agent framework you admire, and receive a structured proposal at docs/research-<repo>-<date>.md covering what to adopt, what to avoid, and how it maps to your codebase. ## Quick Start Research the GitHub repository at https://github.com/example/project and produce a proposal of insights we can apply to our codebase.

Frequently Asked Questions about flywheel-research

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

FAQPage Schema
How do I research a GitHub repository with AI agents?

Provide the repository URL and the Skill runs a 7-phase pipeline: an Explore agent maps architecture and data flows, parallel agents deepen key areas and hunt for blunders, and Plan agents synthesize findings into a written proposal under docs/research/.

What Git hosts and clone URLs are supported?

Only HTTPS URLs on github.com, gitlab.com, bitbucket.org, codeberg.org, and git.sr.ht are accepted by default. HTTP, git, and SSH protocols are refused unless FLYWHEEL_ALLOW_INSECURE_CLONE=1 is set, and private hosts require explicit user confirmation.

Can I use repository research to plan a feature integration?

Yes, the Major Feature Integration Mode adds phases 8-12: an integration proposal document, iterative deepening with an Opus agent, five sequential blunder-hunt passes, and cross-model feedback before a final synthesized recommendation.

How does the research pipeline ensure reproducibility?

After cloning, the pipeline pins the HEAD commit via git rev-parse and records it in the final document as a Source line with the URL and short SHA, so readers can check out the exact commit that was studied.

What happens if a research agent goes idle?

Idle agents are nudged individually with a SendMessage request for findings, and each agent is shut down individually with a shutdown_request message rather than a broadcast, keeping the team coordination explicit and auditable.