Skip to main content
T4 epic · research / consulting / VC: plan-then-execute. A fast model writes the plan, an agent works the web under explicit budgets, a thinking model synthesizes. Three stages, three different cost profiles, every intermediate on disk.

The job

« Get me up to speed on X by Thursday » is two days of tabs, or it’s this pipeline: four sharp queries planned, researched with verbatim quotes and source tracking, synthesized into an executive brief that separates what’s true from what’s contested.

The shape

The file

deep-research-brief.nika.yaml

How it works

1

Right model, right stage

Planning is a haiku-class job (model: override on the task); synthesis gets a thinking: budget. The envelope default covers the middle. One file, three cost profiles.
2

The agent has a leash

max_turns: 25 + max_tokens_total: 150000 bound the loop; nika:done lets it exit cleanly when the plan is exhausted. The final message must match the schema: findings AND sources.
3

Callable by other workflows

The typed outputs: (brief, sources) make this a building block: a parent workflow can consume the contract without parsing prose.

Constructs you just used

Make it yours

  • Force source-grounding harder: have brief cite ${{ tasks.investigate.output.sources }} inline per claim.
  • Competitive variant: seed plan with Competitor radar’s digest instead of a bare topic.
  • Weekly cadence: pair with your scheduler and diff this week’s brief against last week’s with nika:json_diff.

Next · Incident war room

Parallel evidence gathering, a settle-and-recheck loop, and a postmortem that refuses to claim recovery it can’t prove.