Skip to content
Back to skills

Research Flow

ASecurity

Workflow for deep project research with grounded references, parallel exploration, etc.

  • 352 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 3, 2026
ai-agentsrustgo

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add griddynamics/rosetta --skill research-flow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Research Flow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Research Flow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/griddynamics-research-flow-83ab0a63/badge)](https://www.skillsdirectory.com/skills/griddynamics-research-flow-83ab0a63)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: research-flow
description: "Workflow for deep project research with grounded references, parallel exploration, etc."
tags: ["workflow"]
baseSchema: docs/schemas/workflow.md
---

<research_flow>

<description_and_purpose>
Orchestrates deep research via meta-prompting: craft an optimized research prompt, then execute it in a dedicated subagent.
</description_and_purpose>

<workflow_phases>

<prerequisites phase="0", applies="ALL">

1. All Rosetta prep steps MUST be FULLY completed
2. USE SKILL `load-project-context`, `orchestration`, `hitl`
3. MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
4. Orchestrator trusts the system and skills; coordinates sequence, artifacts, state, and approvals only.
5. Workflow state MUST be saved to `agents/TEMP/<FEATURE>/research-flow-state.md` file.
6. If `/goal` is set repeat phases 3-4 until goal is met.

</prerequisites>

<context_load phase="1" subagent="researcher" role="Context gatherer for research scope" subagent_required_model="gpt-5.6-terra-medium">

1. Read all lines from CONTEXT.md, ARCHITECTURE.md, and IMPLEMENTATION.md.
2. Input: user research request. Output: loaded project context.
3. Update `research-flow-state.md`.

</context_load>

<prompt_craft phase="2" subagent="researcher" role="Research prompt architect" subagent_required_model="gpt-5.6-terra-high, gpt-5.6-sol-high">

1. Create an optimized research prompt for the user request.
2. Save as `research-prompt.md` in FEATURE PLAN folder. Output ONLY the optimized prompt.
3. Input: user request + project context. Output: `research-prompt.md`.
4. Required skills: `reasoning`
5. Update `research-flow-state.md`.
6. HITL approval of research prompt before execution.

</prompt_craft>

<execute_research phase="3" subagent="researcher" role="Deep research executor" subagent_required_model="gpt-5.6-terra-medium">

1. Execute the approved research prompt as a separate subagent.
2. Input: approved `research-prompt.md`. Output: `docs/<feature>-research.md`.
3. Required skills: `research`
4. Update `research-flow-state.md`.

</execute_research>

<finalize phase="4" subagent="researcher" role="Research finalizer" subagent_required_model="gpt-5.6-terra-medium">

1. Finalize `docs/<feature>-research.md`.
2. Input: completed research document. Output: finalized research document.
3. Update `research-flow-state.md` and mark complete.

</finalize>

</workflow_phases>

</research_flow>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…