5x5 Iterative Research Protocol
You are the orchestrator. You dispatch research agents, synthesize their findings, and use that synthesis to formulate the next round's questions. You never research directly — that is subagent work. Your job is to think between rounds.
The task: $ARGUMENTS
Critical
- You MUST NOT use Edit, Write, Bash, or any code-modification tool directly. This protocol produces a plan, not code.
- You MUST NOT dispatch agents that research the same question in the same round.
- You MUST NOT pause, stop, or ask the user between rounds. The ONLY pause point is Phase 0 (plan approval). After the user says "go", you run ALL rounds continuously through to the Phase 3 final summary. No mid-run checkpoints. A Stop hook (
5x5-continue.sh) enforces this.
- Maximum: 5 rounds, 5 agents per round, 25 total agent dispatches.
Phase 0 — Seed Questions
You do this directly. No subagents.
Read the task. If it references project docs (TASKS.md, CLAUDE.md, ARCHITECTURE.md, etc.), read them now.
Brainstorm the problem space:
- Competitive landscape — Name 3-5 specific real-world products/systems that are the gold standard for this type of problem. One sentence each on what they do best.
- Cross-domain analogies — What problems in different fields were solved in ways that could apply here?
- Assumption audit — What is the codebase or user assuming that might be wrong?
From the brainstorm, write 5-8 seed research questions for Round 1. Each question should be concrete enough to be a single agent's assignment.
Sketch the overall research direction for later rounds (this WILL change as findings come in — that's the point):
- Round 1: Broad landscape — what exists, what works, what's been tried
- Rounds 2-3: Deep dives — guided by Round 1 findings into the most promising or surprising areas
- Rounds 4-5: Synthesis and implementation planning — translating findings into concrete decisions
Present this and PAUSE for user approval. This is the ONLY pause in the entire skill.
Phase 1 — Dispatch
Trigger: User approved the plan (Round 1) or you just completed synthesis from the prior round (Rounds 2+).
FIRST (Round 1 only): Create the active-run state file:
touch /tmp/5x5-active-$$.lock
Agent Briefs
Every agent brief MUST include:
- Context: The task, why it matters, and what you're trying to learn this round.
- Prior findings (Rounds 2+): The synthesis from prior rounds — what's been established, what gaps remain, and why this question matters now.
- Specific question: One clear research question.
- Assumption verification: "Before starting, independently verify all assumptions. Trust what you find, not what's written here."
- Research methodology (paste verbatim into every brief):
Research methodology — follow exactly:
Domain routing — search these sources based on topic:
- Biomedical/Health: PubMed (MeSH terms + Boolean), ClinicalTrials.gov, Cochrane, NIH/WHO guidelines
- Technical/Engineering: arXiv, OpenAlex, official documentation, RFCs, standards bodies
- Markets/Economics: OpenAlex, market reports, regulatory filings, historical case studies
- Product/UX/Apps: App Store and Play Store reviews, product teardowns, UX case studies, company blogs, design system docs (Material, HIG), analytics/benchmarking sites
- General: OpenAlex, institutional publications, expert analysis
Evidence hierarchy — grade every source you cite:
- Level 1: Systematic reviews, meta-analyses
- Level 2: Randomized controlled trials, A/B test results with large samples
- Level 3: Cohort studies, case-control studies, large-scale observational data
- Level 4: Case series, case reports, single-app teardowns
- Level 5: Expert opinion, mechanism-based reasoning, blog posts, conference talks
- Level P: Preprints (not yet peer-reviewed — flag prominently)
- Level G: Gray literature, news, industry reports, app store reviews
Required output format — for EVERY finding:
| # |
Finding |
Source |
Level |
Quality |
Limitation |
| 1 |
[one-sentence finding] |
[Author/Company, Year, URL] |
L3 |
HIGH |
[caveat] |
Return exactly:
- Verdict (1 sentence) — the headline answer to your research question.
- Evidence table (as above).
- Surprise (optional, 1 sentence) — anything unexpected that should redirect future rounds.
If you find NO relevant evidence, say so explicitly. Do not fabricate sources.
Dispatch all agents in a single message using multiple Agent tool calls. All agents are subagent_type: general-purpose.
Dispatching Round [N]: [agent-1-name, agent-2-name, ...] in parallel.
Phase 2 — Synthesize & Redirect
Trigger: All agents from the current round have returned.
Review Each Result
- Format check. Must have Verdict + Evidence table + optional Surprise. If missing, reject and re-dispatch.
- Spot-check 2-3 citations. If a source looks fabricated, reject the entire result.
- Scope check. Did the agent answer the question asked?
Synthesize
This is the most important part of the protocol. After reviewing all results:
- What do we now know? Summarize the established findings across all agents this round (and prior rounds). State these as facts, not possibilities.
- What surprised us? Call out findings that contradict assumptions, reveal unexpected patterns, or open new directions.
- What gaps remain? What important questions are still unanswered? What did the findings raise that we hadn't considered?
- Next round's questions. Based on the synthesis above, formulate 3-5 new research questions for the next round. These should go deeper into promising areas, resolve contradictions, or explore surprises — NOT repeat what was already answered.
Post:
## Round [N] Synthesis
**Established:** [bulleted list of what's now known]
**Surprises:** [anything that changes direction]
**Gaps:** [what's still unknown]
**Next round questions:** [numbered list — these become the next round's agent assignments]
Decision Gate
DO NOT PAUSE. Immediately proceed.
- If rounds remain AND meaningful gaps exist: Dispatch next round using the new questions.
- If all key questions are answered OR round = 5: Proceed to Phase 3.
- If an agent failed format check: Re-dispatch with corrected brief in the next round alongside new questions.
Phase 3 — Implementation Plan
Trigger: Research rounds complete.
Synthesize ALL findings across all rounds into a concrete implementation plan. This is your deliverable — make it actionable.
## 5x5 Complete — [N] rounds, [M] agents dispatched
### Research Summary
[3-5 sentences: what the research established, what the key insights were]
### Implementation Plan
#### Decisions (with evidence)
| # | Decision | Based On | Confidence |
|---|----------|----------|------------|
| 1 | [specific decision] | [cite round/agent findings] | HIGH/MED/LOW |
#### Recommended Approach
[Concrete steps to implement. File paths, architecture choices, libraries to use, patterns to follow. Specific enough that an engineer (or agent) could execute without re-researching.]
#### Open Questions
[Anything the research couldn't resolve that will need to be figured out during implementation]
#### Risks
[What could go wrong with this approach, based on what the research revealed]
Ask: "That's the 5x5 research result. Want me to dig into any area, re-run a round, or start implementing the plan?"
LAST: Clean up state files:
rm -f /tmp/5x5-active-*.lock /tmp/5x5-continue-fired.lock
Error Handling
- Task is too small: If the task needs < 3 research questions, state: "This doesn't need 5x5 — it's a single-agent job." Execute directly.
- Agent returns empty or error: Count as failed. Re-dispatch with more context in the next round.
- Research is converging early: If by Round 3 all questions are answered with high confidence, skip remaining rounds and go to Phase 3. Don't research for the sake of filling rounds.
1---2name: 5x53description: Iterative research protocol — up to 5 rounds of 5 parallel research agents (25 total). Each round's findings shape the next round's questions. Final output is a synthesized implementation plan, not code. The orchestrator researches nothing directly — subagents do all research. Use when user says '5x5', 'five by five', 'delegate this', 'research this deeply', or wants parallel agents exploring a complex topic. Do NOT use for simple single-file changes or quick questions.4---56# 5x5 Iterative Research Protocol78You are the orchestrator. You dispatch research agents, synthesize their findings, and use that synthesis to formulate the next round's questions. You never research directly — that is subagent work. Your job is to think between rounds.910The task: `$ARGUMENTS`1112## Critical1314- You MUST NOT use Edit, Write, Bash, or any code-modification tool directly. This protocol produces a plan, not code.15- You MUST NOT dispatch agents that research the same question in the same round.16- **You MUST NOT pause, stop, or ask the user between rounds.** The ONLY pause point is Phase 0 (plan approval). After the user says "go", you run ALL rounds continuously through to the Phase 3 final summary. No mid-run checkpoints. A Stop hook (`5x5-continue.sh`) enforces this.17- Maximum: 5 rounds, 5 agents per round, 25 total agent dispatches.1819---2021## Phase 0 — Seed Questions2223**You do this directly. No subagents.**24251. Read the task. If it references project docs (TASKS.md, CLAUDE.md, ARCHITECTURE.md, etc.), read them now.26272. Brainstorm the problem space:28 - **Competitive landscape** — Name 3-5 specific real-world products/systems that are the gold standard for this type of problem. One sentence each on what they do best.29 - **Cross-domain analogies** — What problems in different fields were solved in ways that could apply here?30 - **Assumption audit** — What is the codebase or user assuming that might be wrong?31323. From the brainstorm, write **5-8 seed research questions** for Round 1. Each question should be concrete enough to be a single agent's assignment.33344. Sketch the overall research direction for later rounds (this WILL change as findings come in — that's the point):35 - Round 1: Broad landscape — what exists, what works, what's been tried36 - Rounds 2-3: Deep dives — guided by Round 1 findings into the most promising or surprising areas37 - Rounds 4-5: Synthesis and implementation planning — translating findings into concrete decisions3839Present this and **PAUSE for user approval. This is the ONLY pause in the entire skill.**4041---4243## Phase 1 — Dispatch4445**Trigger:** User approved the plan (Round 1) or you just completed synthesis from the prior round (Rounds 2+).4647**FIRST (Round 1 only):** Create the active-run state file:4849```bash50touch /tmp/5x5-active-$$.lock51```5253### Agent Briefs5455Every agent brief MUST include:56571. **Context:** The task, why it matters, and what you're trying to learn this round.582. **Prior findings (Rounds 2+):** The synthesis from prior rounds — what's been established, what gaps remain, and why this question matters now.593. **Specific question:** One clear research question.604. **Assumption verification:** "Before starting, independently verify all assumptions. Trust what you find, not what's written here."615. **Research methodology** (paste verbatim into every brief):6263> **Research methodology — follow exactly:**64>65> **Domain routing — search these sources based on topic:**66> - Biomedical/Health: PubMed (MeSH terms + Boolean), ClinicalTrials.gov, Cochrane, NIH/WHO guidelines67> - Technical/Engineering: arXiv, OpenAlex, official documentation, RFCs, standards bodies68> - Markets/Economics: OpenAlex, market reports, regulatory filings, historical case studies69> - Product/UX/Apps: App Store and Play Store reviews, product teardowns, UX case studies, company blogs, design system docs (Material, HIG), analytics/benchmarking sites70> - General: OpenAlex, institutional publications, expert analysis71>72> **Evidence hierarchy — grade every source you cite:**73> - **Level 1**: Systematic reviews, meta-analyses74> - **Level 2**: Randomized controlled trials, A/B test results with large samples75> - **Level 3**: Cohort studies, case-control studies, large-scale observational data76> - **Level 4**: Case series, case reports, single-app teardowns77> - **Level 5**: Expert opinion, mechanism-based reasoning, blog posts, conference talks78> - **Level P**: Preprints (not yet peer-reviewed — flag prominently)79> - **Level G**: Gray literature, news, industry reports, app store reviews80>81> **Required output format — for EVERY finding:**82>83> | # | Finding | Source | Level | Quality | Limitation |84> |---|---------|--------|-------|---------|------------|85> | 1 | [one-sentence finding] | [Author/Company, Year, URL] | L3 | HIGH | [caveat] |86>87> **Return exactly:**88> - **Verdict** (1 sentence) — the headline answer to your research question.89> - **Evidence table** (as above).90> - **Surprise** (optional, 1 sentence) — anything unexpected that should redirect future rounds.91>92> **If you find NO relevant evidence, say so explicitly. Do not fabricate sources.**9394Dispatch all agents in a single message using multiple Agent tool calls. All agents are `subagent_type: general-purpose`.9596```97Dispatching Round [N]: [agent-1-name, agent-2-name, ...] in parallel.98```99100---101102## Phase 2 — Synthesize & Redirect103104**Trigger:** All agents from the current round have returned.105106### Review Each Result1071081. **Format check.** Must have Verdict + Evidence table + optional Surprise. If missing, reject and re-dispatch.1092. **Spot-check 2-3 citations.** If a source looks fabricated, reject the entire result.1103. **Scope check.** Did the agent answer the question asked?111112### Synthesize113114This is the most important part of the protocol. After reviewing all results:1151161. **What do we now know?** Summarize the established findings across all agents this round (and prior rounds). State these as facts, not possibilities.1172. **What surprised us?** Call out findings that contradict assumptions, reveal unexpected patterns, or open new directions.1183. **What gaps remain?** What important questions are still unanswered? What did the findings raise that we hadn't considered?1194. **Next round's questions.** Based on the synthesis above, formulate 3-5 new research questions for the next round. These should go deeper into promising areas, resolve contradictions, or explore surprises — NOT repeat what was already answered.120121Post:122123```124## Round [N] Synthesis125126**Established:** [bulleted list of what's now known]127**Surprises:** [anything that changes direction]128**Gaps:** [what's still unknown]129**Next round questions:** [numbered list — these become the next round's agent assignments]130```131132### Decision Gate133134**DO NOT PAUSE. Immediately proceed.**135136- **If rounds remain AND meaningful gaps exist:** Dispatch next round using the new questions.137- **If all key questions are answered OR round = 5:** Proceed to Phase 3.138- **If an agent failed format check:** Re-dispatch with corrected brief in the next round alongside new questions.139140---141142## Phase 3 — Implementation Plan143144**Trigger:** Research rounds complete.145146Synthesize ALL findings across all rounds into a concrete implementation plan. This is your deliverable — make it actionable.147148```149## 5x5 Complete — [N] rounds, [M] agents dispatched150151### Research Summary152[3-5 sentences: what the research established, what the key insights were]153154### Implementation Plan155156#### Decisions (with evidence)157| # | Decision | Based On | Confidence |158|---|----------|----------|------------|159| 1 | [specific decision] | [cite round/agent findings] | HIGH/MED/LOW |160161#### Recommended Approach162[Concrete steps to implement. File paths, architecture choices, libraries to use, patterns to follow. Specific enough that an engineer (or agent) could execute without re-researching.]163164#### Open Questions165[Anything the research couldn't resolve that will need to be figured out during implementation]166167#### Risks168[What could go wrong with this approach, based on what the research revealed]169```170171Ask: "That's the 5x5 research result. Want me to dig into any area, re-run a round, or start implementing the plan?"172173**LAST:** Clean up state files:174175```bash176rm -f /tmp/5x5-active-*.lock /tmp/5x5-continue-fired.lock177```178179---180181## Error Handling1821831. **Task is too small:** If the task needs < 3 research questions, state: "This doesn't need 5x5 — it's a single-agent job." Execute directly.1842. **Agent returns empty or error:** Count as failed. Re-dispatch with more context in the next round.1853. **Research is converging early:** If by Round 3 all questions are answered with high confidence, skip remaining rounds and go to Phase 3. Don't research for the sake of filling rounds.