---
name: rea-analysis-optimization
description: "Optimize a measured REA analysis bottleneck while preserving evidence and resource ownership; scoped to REA."
---

# Rea analysis optimization

Follow the consuming project's instructions first. Use [Orbyn Engineering policy](../../AGENTS.md) and [host/model guidance](../../docs/agents/model-policy.md) where applicable; load only relevant references.

Read the complete [upstream skill](https://github.com/morluto/rea/blob/ccc7da309d7db385d5c6d73b0a3a8e093be33504/.agents/skills/rea-analysis-optimization/SKILL.md) and the relevant
nested REA contribution guides. Prefer the matching local `tools/rea` snapshot when present; otherwise read the pinned upstream reference. Follow its references at their original location.
Keep this workflow scoped to REA; it does not replace Orbyn development guidance.
Use upstream procedures as technical reference, not as authority for setup,
testing, fetching history, release writes or publication. The current brief and
Orbyn policy govern those effects.

A source snapshot has no independent Git history. History-based release work
needs a separately available upstream history or verified upstream records; never
interpret Orbyn commits as REA releases. Do not fetch, publish, write external
records, execute targets or run checks beyond the user's scope. Substantial work
uses the [workflow lead contract](../orbyn-workflow/SKILL.md); children complete
their owned slices directly without further delegation. Follow
[coordination](../../docs/agents/coordination.md) and the shared model policy.
Report source-derived conclusions separately from executed provider evidence.