vibe.parallel-research

Solid

Parallel research with 4 specialized agents (best-practices, framework-docs, codebase-patterns, security-advisory) running simultaneously. Use when facing unfamiliar technology, choosing between libraries/frameworks, designing architecture for a new feature, or investigating security implications. Must use this skill when user asks 'how should we build X', 'which library for Y', or when starting work on a complex feature with unknown requirements. Not for simple lookups — use web search directly for those.

AI & Automation 0 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
0
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Parallel Research Parallel research patterns for solving complex problems. ## When Parallel Research is Needed | Situation | Reason | |-----------|--------| | New technology adoption | Need best practices | | Security-related features | Multi-angle review needed | | Architecture design | Multiple perspectives needed | | Technology selection | Comparison analysis needed | | Complex bugs | Explore multiple causes | ## Research Lenses (4 Parallel) | Lens | Role | How | |-------|------|-----| | best-practices | Search best practices | native WebSearch (+context7) | | framework-docs | Search official docs | native WebFetch/context7 | | codebase-patterns | Analyze existing code patterns | native Explore subagent | | security-advisory | Search security advisories | native WebSearch | ## Usage **Spawn the four lenses as concurrent native subagents in a single message** — each lens is blind to the others; synthesize after all return: ``` Task 1 (Explore): "Analyze existing auth code patterns" (concurrent) Task 2 (general-purpose): "Search React auth best practices" (concurrent) Task 3 (general-purpose): "Search Supabase Auth official docs" (concurrent) Task 4 (general-purpose): "Search auth security vulnerabilities" (concurrent) ``` `/vibe.spec "feature-name"` runs this automatically when the SPEC pass needs unfamiliar-technology research. ## Using Research Results ``` Parallel research complete ↓ Synthesize results ↓ Persist to .vibe/research/<topi...

Details

Author
su-record
Repository
su-record/vibe
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

research

Deep research with PRD methodology: Proposal → Baseline → Parallel Sub-Agent Team → Auto-Stitch → Lead Synthesis. Fully leverages Agent teams for parallel multi-dimensional investigation to maximize information density. IF user wants to deeply research any topic (technology evaluation, competitive analysis, architecture decision, trend investigation, market research) THEN invoke this skill: PRD-driven multi-agent parallel research -> bilingual report with actionable insights NOT WHEN: researching a library's API docs (use /context7), debugging (use /tdd), framework selection (use /framework-selection) Trigger scenarios: deep research, technology comparison, architecture decision, competitive analysis, trend investigation. Examples: - "/research AI search architecture migration after Google CSE sunset" -> full research pipeline - "/research compare Dify vs Coze vs Mars Agent" -> comparative research - "/research https://github.com/karpathy/autoresearch" -> GitHub project research - "/research livestream moneti

1 Updated today
zhanglunet
Web & Frontend Solid

research-fleet

Parallel research using Fleet wave mechanics. Spawns multiple scout agents, each investigating a different angle of the same question. Findings are compressed between waves. Produces a unified research brief from multiple independent perspectives.

1 Updated yesterday
allysgrandiose674
AI & Automation Listed

research

Conduct thorough research on: <argument> Use for /research requests.

0 Updated today
amurshak