Rapid Research Loop
- Repo stars 0
- Author repo FarmFriend-Terminal-React
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Rapid Research Loop
## When to use it
- The user needs a structured briefing, comparison table, FAQ, or short memo derived from multiple sources.
- The task explicitly says "research", "investigate", "summarize", or requests citations/links.
- Another agent already gathered raw notes and you must distill them.
## Guardrails
1. Always collect at least three independent sources unless the user provided authoritative material.
2. Keep a running source log (see `templates/source_log_template.md`) before drafting a summary.
3. Mark uncertainty or missing data instead of fabricating details.
4. Prefer deterministic helper scripts for parsing (CSV/JSON) before reasoning about them.
## Step-by-step workflow
1. **Clarify the question** – restate the core decision or comparison criteria in one paragraph.
2. **Plan the evidence sprint** – list the minimum facts you must confirm; group them by sub-question.
3. **Collect evidence** – for each fact, gather a citation with date, outlet, and a one-sentence pull quote.
4. **Grade sources** – label each entry with `primary`, `secondary`, or `speculative`.
5. **Synthesize** – transform the evidence table into:
- a 3-bullet executive summary,
- a risk/unknowns list,
- and next-step recommendations.
6. **Package output** – use `templates/research_brief_template.md` as the outline and include the source log verbatim at the end.
## Output template
```
## TL;DR (3 bullets)
- ...
## Key Findings
1. Finding + cite
2. ...
## Risks / Unknowns
- ...
## Next Best Actions
- ...
## Source Log
| Source | Date | Key Fact | Link | Confidence |
| --- | --- | --- | --- | --- |
```
## Deterministic helpers to pair with
- `read_file` / `search_code` for mining local notes or logs.
- `analyze_data` for CSV-to-table workflows.
- `tavily_search` or `web_page_reader` for live web lookups.
Sections and files
Listed in source order.
sections -> When to use it → Guardrails → Step-by-step workflow → Output template → Deterministic helpers to pair with
terms -> Clarify the question · Plan the evidence sprint · Collect evidence · Grade sources · Synthesize · Package output
files/cmd -> templates/source_log_template.md · primary · secondary · speculative · templates/research_brief_template.md · read_file · search_code · analyze_data
body sha256 -> 85de7b386007
When to use it
The user needs a structured briefing, comparison table, FAQ, or short memo derived from multiple sources. The task explicitly says "research", "investigate", "summarize", or requests citations/links. Another agent already gathered raw notes and you must distill them.
Guardrails
Always collect at least three independent sources unless the user provided authoritative material. Keep a running source log (see
templates/source_log_template.md) before drafting a summary. Mark uncertainty or missing data instead of fabricating details. Prefer deterministic helper scripts for parsing (CSV/JSON) before reasoning about them.Step-by-step workflow
Clarify the question – restate the core decision or comparison criteria in one paragraph. Plan the evidence sprint – list the minimum facts you must confirm; group them by sub-question. Collect evidence – for each fact, gather a citation with date, outlet, and a one-sentence pull quote. Grade sources – label each entry with
primary,secondary, orspeculative. Synthesize – transform the evidence table into:Deterministic helpers to pair with
read_file/search_codefor mining local notes or logs.analyze_datafor CSV-to-table workflows.tavily_searchorweb_page_readerfor live web lookups.